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

[James Stocks (JIRA)]

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)

[James Stocks (JIRA)]

James Stocks updated an issue

Puppet / PUP-5801 exec resource may lose return code if command terminated

Change By: James Stocks *Reproduction:*  * Open 2 terminals to  a  an agent  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|http://linux.die.net/man/3/sleep].  * Now repeat in Puppet, with a module like: {code}class sleep {

exec { 'sleep_a_while':    command => '/bin/sleep 100',   }

}{code}  * 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: {noformat}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]{noformat}

Add Comment

[James Stocks (JIRA)]

James Stocks updated an issue

Puppet / PUP-5801 exec resource may lose return code if command terminated

Change By: James Stocks Scrum Team: Client Platform

Add Comment

[Henrik Lindberg (JIRA)]

Henrik Lindberg assigned an issue to Unassigned

Puppet / PUP-5801 exec resource may lose return code if command terminated

Change By: Henrik Lindberg Assignee: Kylo Ginsberg

Add Comment

This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)

[Henrik Lindberg (JIRA)]

Henrik Lindberg updated an issue

Puppet / PUP-5801 exec resource may lose return code if command terminated

Change By: Henrik Lindberg Labels: triaged

Add Comment

[Josh Cooper (JIRA)]

Josh Cooper updated an issue

Puppet / PUP-5801 exec resource may lose return code if command terminated

Change By: Josh Cooper Team: Agent

Add Comment

[Josh Cooper (Jira)]

Josh Cooper commented on PUP-5801

Re: exec resource may lose return code if command terminated This issue hasn't seen any activity in a long time, and this situation seems fairly uncommon. I'm going to close for now. Please reopen if it is still an issue.

Add Comment

This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97)