I am on Fedora Core 19 using Puppet version 3.7.4.
When I was trying ensure a service was configured to start I would do
something like:
service { 'someservice':
ensure => 'running',
enable => true,
}
But when I would run puppet apply I would get the following error:
Error: Could not enable someservice: Execution of '/sbin/chkconfig
--add someservice'
returned 1: error reading information on service someservice: No such file or
directory
Error: /Stage[main]/Firewall::Linux::Redhat/Service[someservice]/ensure:
change
from stopped to running failed: Could not enable someservice: Execution of
'/sbin/chkconfig --add someservice' returned 1: error reading information on
service someservice: No such file or directory
However if I told it the provider like:
service { 'someservice':
ensure => 'running',
enable => true,
provider => 'systemd',
}
The puppet apply would work fine. This however makes my resource non
portable to systems not using systemd. Is this a bug of some sort?
Am I doing something wrong?
Thanks...James
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/CAPWHxf%2Bd_eyJRypshq7-G1Wtw0H%2BrYY7pFgRQxDNptc4o32r6g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
