Red Hat Bugzilla – Bug 1341087
Cannot do a compliance check on a host
Last modified: 2016-06-29 12:06:56 EDT
Description of problem: It is not possible to run a compliance check on a host Version-Release number of selected component (if applicable): 5.6.0.8-rc1 How reproducible: always Steps to Reproduce: 1. Add a provider (I used QE's vsphere55) 2. Create some host compliance policy, add a condition to it - I used Tag Location - Chicago 3. Attach the policy to the provider 4. Go to the Hosts, mark one and select Policy / Check compliance of last known configuration 5. An error appears: Host / Node "XYZ": Error during 'Compliance Check': undefined method `validate_check_compliance_queue' for #<ManageIQ::Providers::Vmware::InfraManager::HostEsx:0x0000001217f180> 6. Click to dismiss it, open the host details, do the compliance check from there, the same error appears. Actual results: Desribed in steps Expected results: The compliance should run and finish with Non-Compliant because the tag is not set. Additional info: qe test coverage in test_condition_tag[host] (compliance is the fastest way how to verify that TC).
https://github.com/ManageIQ/manageiq/pull/9084
New commit detected on ManageIQ/manageiq/master: https://github.com/ManageIQ/manageiq/commit/214fccfaa1b1044eae8a48c33582600a0d788da5 commit 214fccfaa1b1044eae8a48c33582600a0d788da5 Author: Bill Wei <bilwei@redhat.com> AuthorDate: Wed Jun 1 10:19:05 2016 -0400 Commit: Bill Wei <bilwei@redhat.com> CommitDate: Wed Jun 1 10:19:05 2016 -0400 Always allow check_compliance for host https://bugzilla.redhat.com/show_bug.cgi?id=1341087 app/models/host.rb | 8 ++++++++ app/models/manageiq/providers/redhat/infra_manager/host.rb | 8 -------- 2 files changed, 8 insertions(+), 8 deletions(-)
Verified fixed in 5.6.0.10-rc2.1.20160607103248_d06c141.
https://github.com/ManageIQ/manageiq/pull/9133
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2016:1348