Use init provider on solaris when managing service #336
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Closed
kenyon
approved these changes
Jun 24, 2022
|
@davemcdonnell thanks for the PR. Can you rebase please? And do you know if the solaris version range in metadata.json is up2date? Lines 45 to 50 in 3ffec12 |
…ing init scripts (as of latest version 9.0.0).
davemcdonnell
force-pushed
the
fix_solaris_service_provider
branch
from
73d64d9 to
6e8ac8c
Compare
|
@bastelfreak I've done the rebase. Im not sure on the metadata.json, I only have access to Solaris 11 to test with. I can't see anything obvious that would change support for 10 or 12 though. |
smortex
approved these changes
Jul 12, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pull Request (PR) description
Puppet on Solaris defaults to the SMF provider for services. Splunk is still using init scripts (as of latest version 9.0.0).
Puppet attempts to enable the service, which causes a catalog failure:
Error: Could not start Service[splunk]: Execution of '/usr/sbin/svcadm enable -rs splunk' returned 1: svcadm: Pattern 'splunk' doesn't match any instances
Error: /Stage[main]/Splunk::Forwarder::Service/Service[splunk]/ensure: change from 'stopped' to 'running' failed: Could not start Service[splunk]: Execution of '/usr/sbin/svcadm enable -rs splunk' returned 1: svcadm: Pattern 'splunk' doesn't match any instances
This Pull Request (PR) fixes the following issues
No bug logged for this