Details
-
Bug
-
Status: Closed
-
Critical
-
Resolution: Fixed
-
None
-
None
-
None
-
2
-
RE 2015-12-23
Description
Using a build of puppet with the fix for PUP-5553, puppet's systemd service provider is unable to manage puppet:
root@yunvikxws2bbrl3:~# /opt/puppetlabs/bin/puppet resource service puppet
|
service { 'puppet':
|
ensure => 'stopped',
|
enable => 'false',
|
}
|
root@yunvikxws2bbrl3:~# /opt/puppetlabs/bin/puppet resource service puppet ensure=running --debug
|
...
|
Debug: Executing: '/bin/systemctl is-active puppet'
|
Debug: Executing: '/bin/systemctl unmask puppet'
|
Debug: Executing: '/bin/systemctl start puppet'
|
Error: Could not start Service[puppet]: Execution of '/bin/systemctl start puppet' returned 6: Failed to start puppet.service: Unit puppet.service failed to load: No such file or directory.
|
Error: /Service[puppet]/ensure: change from stopped to running failed: Could not start Service[puppet]: Execution of '/bin/systemctl start puppet' returned 6: Failed to start puppet.service: Unit puppet.service failed to load: No such file or directory.
|
Debug: Finishing transaction 22258300
|
Debug: Storing state
|
Debug: Stored state in 0.03 seconds
|
Debug: Executing: '/bin/systemctl is-active puppet'
|
service { 'puppet':
|
ensure => 'stopped',
|
}
|
Running systemctl separately shows the same problem:
root@yunvikxws2bbrl3:~# /bin/systemctl start puppet
|
Failed to start puppet.service: Unit puppet.service failed to load: No such file or directory.
|
