Issue #18617 has been updated by Josh Cooper. Status changed from Unreviewed to Needs More Information Priority changed from High to Normal Target version changed from 3.0.3 to 3.x
Hi Vaidas, we fixed issue #10963 in 3.0.2. Is your puppet master on ruby 1.9? Also, I'm retargeting this for 3.x since 3.1 is released and we are not planning any more 3.0.x releases. ---------------------------------------- Bug #18617: Resources chaining with tilde syntax to achieve "notify" does not work https://projects.puppetlabs.com/issues/18617#change-82508 Author: Vaidas Jablonskis Status: Needs More Information Priority: Normal Assignee: Category: Target version: 3.x Affected Puppet version: 3.0.1 Keywords: puppet, compiler, error, dependency Branch: I think it is a bug in the way error is reported or the way syntax is interpreted. My manifest code: exec { 'update-search-endpoints': path => "/usr/bin:/bin:${bl_path}", command => 'search-endpoints.py -q --force sync', refreshonly => true, } File <<| tag == 'endpoint_uri' |>> ~> Exec[update-search-endpoints] As you can see there is a simple Exec resource which runs a simple script when it gets a notification from another resource. In this case, the another resource is bunch of exported file resources which are collected, so if that changes a notification is sent to Exec[update-search-endpoints] resource, but instead I get the below error: err: Could not retrieve catalog from remote server: Error 400 on SERVER: Invalid relationship: File[/etc/dpx.d/endpoints/wseed_node2.foo.local_16215] { notify => Exec[update-search-endpoints]Exec[update-search-endpoints] }, because Exec[update-search-endpoints]Exec[update-search-endpoints] doesn't seem to be in the catalog I am not too sure if that's the error reporting issue or something wrong with my syntax? If I use the following syntax instead of the above one - everything works just fine as expected: File <<| tag == 'endpoint_uri' |>> { notify +> Exec['update-search-endpoints'], } I cannot seem to be able to reproduce in 3.0.2 puppetmaster version. I will update this bug report if I will not be able to reproduce it in 3.0.2. Let me know if this bug has been fixed in 3.0.2 version. Any suggestions? -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" 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-bugs?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
