Bug 751474

Description of problem:
A resource with a pinned definition that has drift is said to be out of compliance. We currently do not have a way for easily reporting resources that are out of compliance, nor do we have a way for tracking when resources come back into compliance. Coming back into compliance means that there is no longer any drift.

We need to be able to show for each definition whether or not it is in or out of compliance. The drift definitions view should be updated to support this. A flag of some sort should be displayed to indicate whether or not the definition is in or out of compliance.

We also the inventory summary in the reports section to show whether or not resources are out of compliance. Note that if a resource has multiple pinned definitions, only one of those definitions has to have drift for the resource to be out of compliance. All of the resource's pinned definitions must have no drift for the resource to be in compliance.

Lastly we are expanding the meaning of compliance slightly to include definitions that are created with a non-existent base directory. The primary reason for this inclusion is because we need a reporting mechanism (at the resource definition level) to indicate if/when a definition is created with a non-existent base directory. A user could have for example made a typo, or the intended directory may not exist on the target machine. If the base directory is later created then the resource should come back into compliance. Note that extending compliance to include non-existent base directories applies to pinned as well as unpinned definitions.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info: