Jira (PUP-5801) exec resource may lose return code if command terminated

[James Stocks (JIRA)]

Title: Message Title

James Stocks created an issue   Puppet / PUP-5801 exec resource may lose return code if command terminated Issue Type: Bug Affects Versions: PUP 4.3.2 Assignee: Kylo Ginsberg Components: Types and Providers Created: 2016/02/02 3:56 AM Environment: el7 Priority: Normal Reporter: James Stocks Reproduction: Open 2 terminals to a host In one terminal, run '/bin/sleep 100' In the other terminal, after a couple of seconds find the pid of sleep and execute 'kill SIGALARM [pid]' In the first terminal, echo $? to see the exit code - note that it is the number of seconds sleep had remaining before it was signalled. Now repeat in Puppet, with a module like: class sleep { exec { 'sleep_a_while': command => '/bin/sleep 100', } } Run Puppet with this module included, and while the catalog run is stuck on the sleep, signal SIGALARM to sleep as before Expected: The exec resource should fail because the returned value is [seconds remaining] and not 0 Actual: The exec does fail, but it appears that the return value has been lost: Info: Using configured environment 'sleep' Info: Retrieving pluginfacts Info: Retrieving plugin Info: Caching catalog for ybbp6dpgky283nf.delivery.puppetlabs.net Info: Applying configuration version '1454413025' Error: /bin/sleep 300 returned instead of one of [0] Error: /Stage[main]/Sleep/Exec[sleep_a_while]/returns: change from notrun to 0 failed: /bin/sleep 300 returned instead of one of [0] Add Comment   This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.