Feature #402
closed
Report noop puppet actions seperately
Added by Mohamed Lrhazi over 14 years ago.
Updated about 13 years ago.
Description
In puppet log, noop operations look like this:
info Puppet Applying configuration version '1286391176'
notice //gu_iptables::redhat/File[iptables]/checksum is {md5}878158421d4824500a101bfea33e60d6, should be md5 (noop)
notice //gu_iptables::redhat/File[iptables]/content is {md5}878158421d4824500a101bfea33e60d6, should be (noop)
info //gu_iptables::redhat/File[iptables] Scheduling refresh of Service[iptables]
notice //gu_iptables::redhat/Service[iptables] Would have triggered refresh from 1 dependencies
This reported by foreman as a successful modification involving two changes.
It would be nice if this was somehow reported as "Changes needed, but not applied"
There is a feature request that seems to be related in puppet: http://projects.puppetlabs.com/issues/3535
Thanks a lot.
- Category set to Puppet Reports
- Target version set to 0.2
- Subject changed from Report noop puupet actions seperately to Report noop puppet actions seperately
- Target version changed from 0.2 to 0.3
- Target version deleted (
0.3)
It would be awesome to have the ability to just audit a server with noop. That could also be handy during a puppet/foreman upgrade by setting all host to noop mode and see what it would do.
Looks similar to http://projects.puppetlabs.com/issues/6537
Probably obvious but, if this gets implemented I guess we should also have an extra status on the Dashboard displaying the "pending update" hosts (or something like it).
I've added 'pending' to the main dashboard reports - the table report and pie chart. This report is hyperlinked, there is a 'status.pending' search for hosts now so its easy to search for these hosts. I've changed pending hosts icon to be a 'warning' instead of 'notice' so its more obvious (I'm open for debate on this - it probably should be user configurable ultimately but I have no idea about what the sensible default is).
Changes squashed and pushed back into my branch.
I was thinking of changing the 'noops' columns to just 'pending' ... would this be less obvious to Puppet users?
Ken Barber wrote:
I was thinking of changing the 'noops' columns to just 'pending' ... would this be less obvious to Puppet users?
Yeah, "pending" makes sense. It is what puppet dashboard uses too.
Okay - I've changed it to 'pending' instead, changes pushed to branch.
- Assignee set to Ken Barber
- Target version set to 1.0
- Status changed from New to Closed
- % Done changed from 0 to 100
somehow git ammend via git gui removed the original author of this patch, full credit goes to Ken, sorry about that mate.
Also available in: Atom
PDF