On Wednesday, March 19, 2014 7:54:27 AM UTC-5, David Portabella wrote:
>
> I have this test.pp example on puppet 3.4.3 on OSX 10.9:
>
> c2 {'test': }
> ->
> c3 {'test': }
>
> define c1 {
> notice "+++"
> file {'/tmp/c1.txt': ensure => present }
> }
>
> define c2 {
> c1 {$name: }
> notice "+++"
> file {'/tmp/c2.txt': ensure => present }
> }
>
> define c3 {
> notice "+++"
> file {'/tmp/c3.txt': ensure => present }
> }
>
> running:
>
> $ puppet apply --graph test.pp
>
> produces this graph
> /Users/david/.puppet/var/state/graphs/relationships.dot,
>
> *which shows that /tmp/c3.txt does not require /tmp/c2.txt.*
>
> *why?*
>
I don't know, and your graph did not come across. However, it may simply
be a case of Puppet optimizing. Two unrelated File resources cannot have a
*bona
fide* ordering relationship between them, because syncing one in no way
affects syncing the other.
Still, I find it surprising. Is there at least a chain of relationships
that will cause File['/tmp/c2.txt'] to be applied before
File['/tmp/c3.txt']? Are you sure the catalog you analyzed corresponds to
the version of your manifest set that contains the chain operator you
depict?
John
--
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 view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/5d9023f5-5fd0-45c0-8d51-ceacee1bedb9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
