Jira (PUP-6971) configuration_version undefined on catalog compile failure

[James powis (JIRA)]

James powis created an issue

Puppet / PUP-6971 configuration_version undefined on catalog compile failure Issue Type: Bug Affects Versions: PUP 4.0.0 Assignee: Unassigned Components: Puppet Server Created: 2016/12/04 3:57 PM Environment: Opensource Puppetserver 4.0.0-4.Latest Priority: Normal Reporter: James powis When a catalog compile fails the puppet report self.configuration_version is set to undef. This value is used to reference puppetdb reports using custom reporting (such as puppet-hipchat) Ideally even if the config does not change (due to failure / caching / 0 resources chaged) configuration_version should be generated and rotated for each run regardless of success. Reference: https://github.com/jamtur01/puppet-hipchat/issues/51 Add Comment

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

[Karen Van der Veer (JIRA)]

Karen Van der Veer updated an issue

Puppet / PUP-6971 configuration_version undefined on catalog compile failure

Change By: Karen Van der Veer Component/s: Puppet Server

Add Comment

[Henrik Lindberg (JIRA)]

Henrik Lindberg updated an issue

Puppet / PUP-6971 configuration_version undefined on catalog compile failure

Although the description says "compilation fails", this looks like an agent side thing because it involves sending a report. Change By: Henrik Lindberg Team: Agent & Platform

Add Comment

[James powis (JIRA)]

James powis commented on PUP-6971

Re: configuration_version undefined on catalog compile failure The easiest way to invoke this is to add a fail('foo') into an included manifest.

Add Comment

[John Duarte (JIRA)]

John Duarte updated an issue

Puppet / PUP-6971

configuration_version undefined on catalog compile failure

Change By: John Duarte Labels: triaged

Add Comment

[Josh Cooper (Jira)]

Josh Cooper commented on PUP-6971

Re: configuration_version undefined on catalog compile failure If the agent can't get a catalog from the server, then we won't know what the configuration_version is/should be, and can't include it in the report. There is a transaction_uuid in the report which makes it possible to distinguish among agent runs for the same host. Going to close this as won't do

Add Comment

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