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"

Associated revisions

This change adds the ability to see noops in metric reports insideforeman graphs, charts and lists. The business reason for this is to allowusers to run their puppet agents in noop mode, and see where nodes haveconverged within the foreman dashboard and various foreman reports.

The status data was always stored in the database, we just had to modifythe views and model to get at it.

This change modifies the dashboard adding the new state 'pending' so it appearsin the pie graph, and adds pending to the report view in the dashboard as well.

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).