Bug 1478949 - Control policy doesn't mark an item as Non-Compliant
Control policy doesn't mark an item as Non-Compliant
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Control (Show other bugs)
All All
medium Severity high
: GA
: cfme-future
Assigned To: Lucy Fu
Dmitry Misharov
Depends On:
  Show dependency treegraph
Reported: 2017-08-07 10:47 EDT by Dmitry Misharov
Modified: 2018-07-04 02:04 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Dmitry Misharov 2017-08-07 10:47:08 EDT
Description of problem:
A control policy with action "Mark as Non-Compliant" doesn't do anything.

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

How reproducible:

Steps to Reproduce:
1. Create a control policy with some events, e.g. VM Reset
2. Assign action "Mark as Non-Compliant" to that event to the list of the actions "if all Conditions are True"
3. Assign the policy to a policy profile.
4. Assign the policy profile to some vm.
5. Reset the vm.
6. Refresh the details screen of the vm.

Actual results:
Compliance status is not changed.

Expected results:
Compliance status should be "Non-compliant".

Additional info:
policy.log shows that the vm was marked as non-compliant:
MIQ(action_compliance_failed): Now executing [Mark as Non-Compliant] of ManageIQ::Providers::Vmware::InfraManager::Vm

Note You need to log in before you can comment on or make changes to this bug.