This repository has been archived by the owner on Feb 20, 2020. It is now read-only.
Using correct service manager to handle goagents. #52
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.
Forced the "service" service manager in service module through "use" argument.
The service module actually uses system specific modules, it uses the value of the 'ansible_service_mgr'. In RHEL 7.2 this means 'systemd' which ignore the /etc/init.d/go-agent? scripts. Forcing the "service" option must work on every OS.
This bug caused to task "Ensure Go-agents are not running yet (waiting for server config), but are enabled on startup." to always fail in RHEL 7.2.