New commit detected on ManageIQ/manageiq-providers-ovirt/gaprindashvili: https://github.com/ManageIQ/manageiq-providers-ovirt/commit/f26df63e4c6676bfdc967e80b1be4a0a82435d98 commit f26df63e4c6676bfdc967e80b1be4a0a82435d98 Author: Moti Asayag <masayag> AuthorDate: Sun Apr 1 03:56:49 2018 -0400 Commit: Moti Asayag <masayag> CommitDate: Sun Apr 1 03:56:49 2018 -0400 Merge pull request #232 from borod108/bugs/discovery1559796 Fix provider discovery (cherry picked from commit 9e95b90ada4f822ae971fc2565bd46d1f0e82255) Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1562788 app/models/manageiq/providers/redhat/discovery.rb | 6 +- 1 file changed, 3 insertions(+), 3 deletions(-)
I tried to verify the bug but I came to conclusion that discovering RHV provider does not work as expected. I tried to provide valid IP range. It is true that my RHV provider was discovered, but even after manually refreshing relationships and waiting for some time, the provider had no subordinate inventory. That is no clusters, hosts, datastores, VMs or templates have been displayed in UI although they are present on the provider side. Video and evm.log from verification are in the attachment. Tested on: CFME 5.9.2.2.20180410215257_6961422 RHV 4.2.2.5
Hi, Perhaps there is a missing part in the video, but it seems there were no credentials set for the discovered provider. As per documentation: https://access.redhat.com/documentation/en-us/red_hat_cloudforms/4.6/html/managing_providers/infrastructure_providers#discovering_multiple_management_systems One has to edit the provider after it has been discovered and add its credentials before it can be used.
Boris is right, I was missing last step in the verification. Tried it again and discovery works as expected. Moving to verified status. Thank you for catching that Boris!
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