It is happening on 0.25.5-1 server, but so far I have only seen the problem on 0.24.X clients. I don't have an 0.25.4 master to test against, but at any rate I am unable to reproduce the problem. The problem seems to have occurred in a relatively small time across the affected clients, and hasn't happened again (yet).
I have seen errors similar to the following on all of the affected clients. The "'@name=" variable has a different value on different clients: ./puppet.log:Mon Jun 14 00:05:26 EDT 2010 Puppet (err): Could not apply complete catalog: Invalid 'should' value for mode: #<YAML::Syck::BadAlias:0xb7dbdf94 @name="id050"> I agree that it sounds like a bug. I'm hoping that getting all of my clients up to date will prevent another occurrence. On Jun 15, 10:44 pm, Ohad Levy <ohadl...@gmail.com> wrote: > if this happens on a 0.25.5 server (and maybe client), it might be happening > because of the zaml implementation, can you reproduce this problem with > 0.25.4 master? > > in anycase, it sounds like a bug :) > > Ohad > > On Wed, Jun 16, 2010 at 9:35 AM, Nigel Kersten <nig...@google.com> wrote: > > > On Tue, Jun 15, 2010 at 6:32 PM, donavan <dona...@desinc.net> wrote: > > >> On Jun 15, 2:39 pm, "Gus F." <gus.fer...@gmail.com> wrote: > >> > I am using puppet (version 0.25.5-1.e15 for redhat) for password > >> > management for non-system users. This morning, users on some of my > >> > puppet clients had their encrypted password strings in /etc/shadow > >> > replaced with the following string: > > >> > YAML::syck::BadAlias > > >> Whoa. I just saw this on a .24.8 client for the first time today. I > >> poked at it for a few minutes and couldnt reproduce, so I shrugged it > >> off. > > >> This is what I found in syslog: > >> puppetd: Starting catalog run > >> puppetd: (//#<YAML::Syck::BadAlias:0x2a98ef0a20>/File[/usr/local/bin/ > >> concatfragments.sh]) Failed to retrieve current state of resource: > >> can't convert YAML::Syck::BadAlias into Integer > >> puppetd: (//#<YAML::Syck::BadAlias:0x2a9859e940>/Concat[/etc/ > >> filename.txt]/Exec[concat_/etc/filename.txt]) Dependency file[/usr/ > >> local/bin/concatfragments.sh] has 1 failures > >> puppetd: (//#<YAML::Syck::BadAlias:0x2a9859e940>/Concat[/etc/ > >> filename.txt]/Exec[concat_/etc/filename.txt]) Skipping because of > >> failed dependencies > >> puppetd: (//#<YAML::Syck::BadAlias:0x2a9859e940>/Concat[/etc/ > >> filename.txt]/File[/etc/filename.txt]) Dependency file[/usr/local/bin/ > >> concatfragments.sh] has 1 failures > >> puppetd: (//#<YAML::Syck::BadAlias:0x2a9859e940>/Concat[/etc/ > >> filename.txt]/File[/etc/filename.txt]) Skipping because of failed > >> dependencies > >> puppetd: Finished catalog run in 9.82 seconds > > >> > What could have caused this? > > >> +1 to this. Where to even look? > > > The first thing to do is to work out whether this has occurred with any > > resource types other than Concat, so we know whether this is an issue in the > > core puppet distribution or just in the concat type/provider. > > >> -- > > >> You received this message because you are subscribed to the Google Groups > >> "Puppet Users" group. > >> To post to this group, send email to puppet-us...@googlegroups.com. > >> To unsubscribe from this group, send email to > >> puppet-users+unsubscr...@googlegroups.com<puppet-users%2bunsubscr...@googlegroups.com> > >> . > >> For more options, visit this group at > >>http://groups.google.com/group/puppet-users?hl=en. > > > -- > > nigel > > > -- > > You received this message because you are subscribed to the Google Groups > > "Puppet Users" group. > > To post to this group, send email to puppet-us...@googlegroups.com. > > To unsubscribe from this group, send email to > > puppet-users+unsubscr...@googlegroups.com<puppet-users%2bunsubscr...@googlegroups.com> > > . > > For more options, visit this group at > >http://groups.google.com/group/puppet-users?hl=en. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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.
