Jira (PUP-3184) Exec resource executed even though warning reports it being skipped

[Jay Wallace (JIRA)]

Title: Message Title

Jay Wallace created an issue   Puppet / PUP-3184 Exec resource executed even though warning reports it being skipped Issue Type: Bug Affects Versions: 3.6.2 Assignee: Kylo Ginsberg Components: Types and Providers Created: 04/Sep/14 2:17 PM Environment: Centos 6.5 (PE 3.3.1) Labels: customer Priority: Critical Reporter: Jay Wallace It looks like refresh is triggered and the exec resource is being executed even though it reports the resource being skipped. This appears to be exclusive when notifying a resource with a require. Example: file { '/tmp/foo': content => "test", notify => Exec['/bin/touch /tmp/bar'] } exec { 'config': command => '/bin/false' } exec { '/bin/touch /tmp/bar': refreshonly => true, require => Exec['config'] } In this test both `/tmp/bar` and `/tmp/foo` get created. This is not expected behavior. One would expect the file resource to notify the `/bin/touch /tmp/bar`, skip this resource due to dependencies, and fail when`/bin/false` returns a non-zero exit code. I have been able to work around this using: file { '/tmp/foo': content => "test", notify => Exec['/bin/touch /tmp/bar'], require=> Exec['config'] } exec { 'config': command => '/bin/false' } exec { '/bin/touch /tmp/bar': refreshonly => true, } Add Comment   This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.