Jira (PUP-2827) Don't update lastrunreport and lastrunsummary in noop

[Josh Cooper (Jira)]

Josh Cooper updated an issue

Puppet / PUP-2827 Don't update lastrunreport and lastrunsummary in noop Change By: Josh Cooper Summary: Incorrect return code for -- Don't update lastrunreport and lastrunsummary in noop Add Comment

This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)

[Josh Cooper (Jira)]

Josh Cooper updated an issue

Puppet / PUP-2827 Don't update lastrunreport and lastrunsummary in noop Change By: Josh Cooper

t.pp -- {code:puppet} node default { } {code} running ```puppet apply --noop t.pp``` Running under 3.6.2 returns 1 with the following errors: {noformat} Error: Failed to apply catalog: Operation not permitted - /var/lib/jenkins/.puppet/var/state/state.yaml20140624-3338-egqchx Error: Could not save last run local report: Operation not permitted - /var/lib/jenkins/.puppet/var/state/last_run_summary.yaml20140624-3338-187sv5a Error: Could not send report: Operation not permitted - /var/lib/jenkins/.puppet/var/state/last_run_report.yaml20140624-3338-djuxtb Running under 3.2.4 returns 0 with following output: Notice: Finished catalog run in 1.93 seconds {noformat} If this change was/is desired behaviour (not to us, but perhaps that decision was made), would be great to have an additional flag to turn off that behaviour for automated testing.

Add Comment