Description of problem: ------------------------ Topology View for HyperV is missing all relationships. Version-Release number of selected component (if applicable): ------------------------------------------------------------- 5.8 Alpha 2 How reproducible: ---------------- Always Steps to Reproduce: ------------------- 1. 2. 3. Actual results: -------------- Expected results: ----------------- Additional info: ----------------
*** Bug 1440266 has been marked as a duplicate of this bug. ***
This is happening only if the hosts are not attached to a cluster, for any provider that supports clusterless hosts.
https://github.com/ManageIQ/manageiq-ui-classic/pull/1156
https://github.com/ManageIQ/manageiq/pull/14884
New commit detected on ManageIQ/manageiq/master: https://github.com/ManageIQ/manageiq/commit/d54d057ced78e47353f8fe864337a9f2b53f0131 commit d54d057ced78e47353f8fe864337a9f2b53f0131 Author: Dávid Halász <dhalasz> AuthorDate: Tue Apr 25 19:57:38 2017 +0200 Commit: Dávid Halász <dhalasz> CommitDate: Tue Apr 25 19:58:01 2017 +0200 Add a method to InfraManager to retrieve Hosts without EmsCluster https://bugzilla.redhat.com/show_bug.cgi?id=1440263 app/models/manageiq/providers/infra_manager.rb | 4 ++++ 1 file changed, 4 insertions(+)
New commit detected on ManageIQ/manageiq-ui-classic/master: https://github.com/ManageIQ/manageiq-ui-classic/commit/4e23c99b60f467481ac0ddcdeab6548316aad931 commit 4e23c99b60f467481ac0ddcdeab6548316aad931 Author: Dávid Halász <dhalasz> AuthorDate: Tue Apr 25 19:55:54 2017 +0200 Commit: Dávid Halász <dhalasz> CommitDate: Tue Apr 25 21:20:43 2017 +0200 Connect clusterless hosts directly to the provider in infra topology https://bugzilla.redhat.com/show_bug.cgi?id=1440263 app/services/infra_topology_service.rb | 6 +++++- app/services/topology_service.rb | 2 +- 2 files changed, 6 insertions(+), 2 deletions(-)
I merged the above changed into 5.8.0.11 manually and verified the fix. I'll take care of properly verifying this bug when it hits a real downstream build.
*** Bug 1412336 has been marked as a duplicate of this bug. ***