I would love to, but I have a few questions, is there a apt-repository that has the latest puppet, or do I have to build and manually deploy?
I am using the latest Jaunty 9.04 image built by Alestic: http://alestic.com/ Which uses the cannonical or rightscale apt-repository ec2-mirrors. So I suppose they are the latest puppet packages available. Or are they available somewhere else? Andrew Shafer wrote: > > Fernando, > > No worries, hopefully it will help someone. > > The differences from version to version hasn't been documented in a way > that always makes it obvious. I'm glad you were able to figure out your > problem on 0.24.5. > > If possible, I recommend getting to 0.24.8. > > > > On Thu, Jul 16, 2009 at 12:09 AM, Fernando Padilla <[email protected] > <mailto:[email protected]>> wrote: > > > doing some late night googling: > > > the description of the bug: > https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/368832 > > which was supposed to have been fixed in some version of puppet > (0.24.6), while I'm currently running with 0.24.5. > > > > Another thread talks about the Package provider: > > http://groups.google.com/group/puppet-users/browse_thread/thread/f9d0613fc890e4e3 > > And gave me this idea; to add the following at the very top of site.pp: > > Service { > provider => debian > } > > And so far, it looks like it works. > > > Please excuse me for emailing the list for something that I eventually > figured out.. hopefully others will find this useful (and someone will > set me straight if there are better options.. :) > > > > Fernando Padilla wrote: > > I just saw this in the logs.. maybe it's a clue. > > > > Jul 16 05:47:34 (none) puppetd[11187]: Found multiple default > providers > > for service: freebsd, debian; using freebsd > > > > I might have to force the platform somehow to be debian or ubuntu?? > > > > > > > > Fernando Padilla wrote: > >> 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 [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
