Have anyone of you every seen puppet invert a dependency?
Say I have a class like so:
class jenkins {
user {"jenkins":
ensure => present,
}
}
That should form a dependency like so User[jenkins] => Class[jenkins].
That dependency means that the user jenkins will be done before Class
jenkins. However every once (twice now) something disturbs pupplets
delicate sensibilities and it seems to create a new dependency that goes
backward from what it is supposed to. This causes a dependency cycle and
breaks my catalog. Right now I have a git module checking out the source
for a jenkins server. I end up with a dependency cycle like this:
(Exec[git_http://[email protected]/somevalidgiturl] =>
Git::Repo[http://[email protected]/somevalidgiturl] => Class[Jenkins] =>
User[jenkins] => Exec[git_http://[email protected]/somevalidgiturl])
Notice how it now says Class[Jenkins] needs to be done before
User[jenkins]. But the jenkins user is defined in the class jenkins. So
the dependency should be the other way, It seems to have inverted that
dependency. I have found that if I tweak with related components of the
catalog then it will go away.
https://projects.puppetlabs.com/issues/19718
--
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 [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
