Details
-
Bug
-
Status: Resolved
-
Normal
-
Resolution: Fixed
-
PUP 3.8.8
-
RedHat 7.X - systemd
-
-
Puppet Developer Experience
-
1
-
PDS 2016-11-30
-
Bug Fix
-
The systemd provider now considers services with the 'indirect' enabled state to be disabled.
-
No Action
-
annoyance. covered well by mocked unit tests
Description
Following occurs with each puppet run, which causes annoyance:
Service[rpcbind]/enable: enable changed 'true' to 'false'
The rpcbind service returns "indirect" as a status to is-enabled
_*/bin/systemctl is-enabled rpcbind
indirect*_
This presumably causes puppet to constantly think it's not turned off (standard output should be enabled/disabled
Additional info from systemctl
_*/bin/systemctl status rpcbind.service
รข rpcbind.service - RPC bind service
Loaded: loaded (/usr/lib/systemd/system/rpcbind.service; indirect; vendor preset: enabled)
Active: inactive (dead)*
_
Note that a workaround is to set enable to "true" and ensure to "stopped" to keep it stopped, BUT that requires the hosts to have rpcbind installed - if it is not then it produces an error in the puppet run.
Attachments
Issue Links
- relates to
-
PUP-7163 regression - systemd provider does not honor documented enabled states
-
- Resolved
-