I'm just starting to learn puppet, and I'm using the lates ubuntu jaunty
image on ec2.
I noticed a random service that I wanted to shutdown so I added this:
class no_avahi {
service { "avahi-daemon":
ensure => false
}
}
And it sort-of worked, except this is what happened on the client:
Jul 16 05:32:56 domU-12-31-39-00-85-68 puppetd[4101]:
(//Node[default]/no_avahi/Service[avahi-daemon]/ensure) change from
running to stopped failed: Could not stop Service[avahi-daemon]:
Execution of '/etc/init.d/avahi-daemon onestop' returned 1: at
/etc/puppet/manifests/site.pp:30
It tried to run '/etc/init.d/avahi-daemon onestop', which looks like is
invalid for most scripts under init.d (it should be simply 'stop', not
'onestop').
I have fixed it in my site.pp by adding my own stop command (stop =>
"/etc/init.d/avahi-daemon stop"), but I was just expecting puppet to
simply work..
why is it confused in this instance?
can we file a bug report?
is it my ubuntu image is not standard? Or puppet just confused somehow?
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---
