On Thu, Sep 26, 2013 at 5:21 PM, jcbollinger <john.bollin...@stjude.org>wrote:
>
>
> On Thursday, September 26, 2013 3:11:24 PM UTC-5, Wolf Noble wrote:
>>
>> Hi Sergey,
>>
>> I've noticed behavior similar to then when resource ordering is specified
>> outside of a class; something like this:
>>
>> #foo class
>> #
>> #
>> Class['prereq'] -> Class['foo']
>> class foo() {
>> #some stuff here
>> }
>>
>> since that dependency isn't occurring INSIDE the boundary of
>> Class['foo'], there can be weirdness.
>>
>> I'm not certain that's what's going on for you, but I have seen that same
>> behavior in those instances.
>>
>>
>
> I have trouble believing that an error arising from such a cause would
> randomly appear and disappear as Sergey describes his doing. Something
> must be changing on the master between runs.
>
> With that said, there have been a few similar issues reported in the past;
> generally they seem to be triggered by manifest files being edited, and
> often they are resolved by restarting the master. If Sergey's master is
> running under Passenger then he may be getting new masters starting
> frequently enough to explain the problem disappearing. I can't immediately
> explain why the problem seems pinned to one node, but perhaps this will
> serve as a clue.
>
>
> John
>
What I've seen is that a dependency derived from catalog/nodeA, when NOT
inside a class, can be inconsistently "inherited" by catalog/nodeB if
catalog compilation is occurring at the same time, or soon after A.
I'm not sure if this still occurs >3.x
--
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.
