Jira (PUP-5715) Broken catalog if Puppet is restarted while applying a catalog

[Cesar (JIRA)]

Title: Message Title

Cesar created an issue   Puppet / PUP-5715 Broken catalog if Puppet is restarted while applying a catalog Issue Type: Bug Affects Versions: PUP 3.3.2 Assignee: Unassigned Created: 2016/01/15 1:36 AM Environment: RHEL 6.6 Priority: Normal Reporter: Cesar Restarting the Puppet agent service in the middle of a catalog run sometimes results in a Could not run: source did not contain any PSON! error. Dec 20 07:19:12 helios puppet-master[2709]: Compiled catalog for helios in environment production in 4.85 seconds Dec 20 07:19:15 helios puppet-agent[20563]: Caught TERM; calling stop Dec 20 07:19:15 helios puppet-master[2709]: (//helios/Puppet) Caught TERM; calling stop Dec 20 07:19:18 helios puppet-agent[22331]: Reopening log files Dec 20 07:19:18 helios puppet-agent[22331]: Starting Puppet client version 3.3.2 Dec 20 07:19:18 helios puppet-agent[22331]: Could not run: source did not contain any PSON! Dec 20 07:19:19 helios puppet-agent[22329]: source did not contain any PSON! After that Puppet does not run again (even if it is configured to run periodically) and requires a manual restart to work again. Checking in Jira PUP-1743 seems to be related, but I am not sure if the issue is exactly the same. 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.