New commit detected on ManageIQ/manageiq-providers-ovirt/gaprindashvili: https://github.com/ManageIQ/manageiq-providers-ovirt/commit/95115c13cf152a038af1ae366ef31ac1db112530 commit 95115c13cf152a038af1ae366ef31ac1db112530 Author: Moti Asayag <masayag> AuthorDate: Thu Mar 1 05:52:57 2018 -0500 Commit: Moti Asayag <masayag> CommitDate: Thu Mar 1 05:52:57 2018 -0500 Merge pull request #211 from borod108/cust_attrs Fix graph refresh fetching custom attributes (cherry picked from commit 8f9f2252f7881bf577b29efda25334526c6f70a4) Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1559624 app/models/manageiq/providers/redhat/infra_manager.rb | 1 + app/models/manageiq/providers/redhat/inventory/parser/infra_manager.rb | 11 +- app/models/manageiq/providers/redhat/inventory/persister/infra_manager.rb | 2 +- app/models/manageiq/providers/redhat/inventory/persister/target_collection.rb | 5 +- app/models/manageiq/providers/redhat/inventory_collection_default/infra_manager.rb | 17 + spec/models/manageiq/providers/redhat/infra_manager/refresh/refresher_4_custom_attributes_spec.rb | 50 + spec/models/manageiq/providers/redhat/infra_manager/refresh/refresher_graph_target_vm_spec.rb | 6 +- spec/vcr_cassettes/manageiq/providers/redhat/infra_manager/refresh/ovirt_sdk_refresh_graph_target_vm.yml | 18 + spec/vcr_cassettes/manageiq/providers/redhat/infra_manager/refresh/ovirt_sdk_refresh_recording_custom_attrs.yml | 6833 + 9 files changed, 6934 insertions(+), 9 deletions(-)
Marking as a blocker as RHV would like to switch to graph refresh by default in 5.9.2
Verification steps: 1. Have a VM on RHV provider and set graph_refresh to true on CFME appliance 2. Set custom attribute sap_agent == false on your VM and refresh provider 3. Custom attribute cannot be seen in CFME UI - that is an expected behaviour since applying of custom attribute require's VM reboot 4. Reboot VM and refresh provider Actual result: Custom attribute can be seen in CFME UI Verified on: CFME 5.9.2.2 RHV 4.2.2.5
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/RHSA-2018:1328