Jira (PUP-6210) Report overall status should not be noop because of only one noop resource

Fabien Malfoy (JIRA)

unread,

Apr 21, 2016, 12:03:04 PM4/21/16

to puppe...@googlegroups.com

Fabien Malfoy created an issue

Puppet /

PUP-6210

Report overall status should not be noop because of only one noop resource

Issue Type:	Improvement
Affects Versions:	PUP 4.4.1
Assignee:	Kylo Ginsberg
Components:	Catalog Application, PE
Created:	2016/04/21 9:02 AM
Environment:	Behaviour witnessed on PE 2016.1.1 with the Puppet classroom environment VMs (puppet-training-4.1.ova and puppet-student-4.2.ova)
Priority:	Normal
Reporter:	Fabien Malfoy

The enforcement of a catalog containing at least one noop resource (with the noop metaparameter)

that should have been triggered will have an overall status of noop reported (and thus the associated grey icon shown, along with the relevant number of nodes increased in the radiator view of the PE Console), regardless of any other change event during the run.

The report should in fact report an overall status of either changed or unchanged (depending on whether enforced resources effectively have changed or not), leaving the noop status for a global --noop run.

While the issue has been tested on PE, this has been posted in PUP since it may be more related to the way the puppet agent is reporting runs outcome.

Add Comment

This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)

Kylo Ginsberg (JIRA)

unread,

Apr 21, 2016, 12:19:05 PM4/21/16

to puppe...@googlegroups.com

Kylo Ginsberg updated an issue

Puppet /

PUP-6210

Report overall status should not be noop because of only one noop resource

Change By:	Kylo Ginsberg
Scrum Team:	Client Platform

Add Comment

Kylo Ginsberg (JIRA)

unread,

Apr 21, 2016, 12:21:06 PM4/21/16

to puppe...@googlegroups.com

Kylo Ginsberg commented on

PUP-6210

Re: Report overall status should not be noop because of only one noop resource

Ping Branan Riley, Verne Lindner, as I know you've both been looking at statuses from different angles.

Add Comment

Verne Lindner (JIRA)

unread,

Apr 21, 2016, 11:09:31 PM4/21/16

to puppe...@googlegroups.com

Verne Lindner commented on

PUP-6210

Re: Report overall status should not be noop because of only one noop resource

Karel Brezina With the new CM dashboard run status designations, are we ignoring resource no-op flags when determining run status?

Add Comment

Karel Brezina (JIRA)

unread,

Apr 22, 2016, 2:54:03 AM4/22/16

to puppe...@googlegroups.com

Karel Brezina commented on

PUP-6210

Re: Report overall status should not be noop because of only one noop resource

Verne Lindner Yes, we only read the overall noop flag set on reports entity.

Add Comment

Fabien Malfoy (JIRA)

unread,

May 2, 2016, 2:31:03 AM5/2/16

to puppe...@googlegroups.com

Fabien Malfoy commented on

PUP-6210

Re: Report overall status should not be noop because of only one noop resource

So, does my request make sense to any of you ?

Add Comment

This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)

Verne Lindner (JIRA)

unread,

May 2, 2016, 10:14:09 AM5/2/16

to puppe...@googlegroups.com

Verne Lindner commented on

PUP-6210

Re: Report overall status should not be noop because of only one noop resource

Fabien Malfoy With the next PE release, the PE console will display run statuses with event types failed, changed, or unchanged and whether or not the run occurred in no-op mode; the no-op resource flag alone will no longer determine run status. It sounds like that should address the issue you describe?