Issue #18677 has been updated by Reid Vandewiele. Status changed from Unreviewed to Duplicate
Yep, in Puppet 2.7.20 this issue is resolved (I was using 2.7.19). Seems to be related most directly to the later discussion in #7422. ---------------------------------------- Bug #18677: Resource chain operators conflict uncleanly with inline metaparameter specification https://projects.puppetlabs.com/issues/18677#change-81547 Author: Reid Vandewiele Status: Duplicate Priority: Normal Assignee: Category: language Target version: Affected Puppet version: Keywords: Branch: Consider the following Puppet code as "example1.pp": notify { 'serenity': } notify { 'firefly': } notify { 'alliance': notify => Notify['serenity'] } Notify['alliance'] ~> Notify['firefly'] Running `puppet apply example1.pp` produces the following output: undefined method `<<' for {}:Hash on node pseudonix.local Similarly, "example2.pp": notify { 'serenity': } notify { 'firefly': } notify { 'alliance': before => Notify['serenity'] } Notify['alliance'] -> Notify['firefly'] The same output is produced: undefined method `<<' for {}:Hash on node pseudonix.local This is buggy behavior. Ideally when there is a conflict the behavior should be additive. At the end of day in example1.pp there should exist notify relationships such that 'alliance' notifies 'serenity' AND 'alliance' notifies 'firefly'. -- 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 post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
