On Feb 17, 2009, at 8:53 PM, Matt McLeod wrote:
>
> The greatly-simplified case works fine, or at least has done across
> a couple of platforms for 24 hours.
>
> A few hours ago I changed the proof-of-concept package management
> version to place the schedule inside the class. i.e., rather than:
>
> schedule{blah:}
> define moreblah {..., schedule=>blah}
> class theclass {moreblah{foo:}}
>
> it's now
>
> define moreblah {..., schedule=>blah}
> class theclass {
> schedule{blah:}
> moreblah{wibble:}
> }
>
> and it *seems* to be working. I can only assume that sometimes it
> was parsing the class before the schedule, even though the schedule
> was defined before the class in the same file in the manifest, but
> now that the schedule is defined *in* the class the ordering is
> working
> out OK.
I verified that parse order, and any other kind of order, couldn't
cause this problem - the schedule isn't looked up until the whole
catalog is instantiated.
BTW, one relatively easy way to test on the hosts that are failing -
look in the cached catalog yaml file and see if the schedule is
actually in there. Because it sounds like you're just not getting
that schedule.
--
Criminal: A person with predatory instincts who has not sufficient
capital to form a corporation. --Howard Scott
---------------------------------------------------------------------
Luke Kanies | http://reductivelabs.com | http://madstop.com
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
