Red Hat Bugzilla – Bug 1289590
Provider event results show hyper link of the provider name which leads to the infrastructure provider which never existed
Last modified: 2016-02-10 10:26:06 EST
+++ This bug was initially created as a clone of Bug #1288131 +++ Description of problem: in the provider's result, we get a link in the container to the provider in the infrastructure main page. since I never created a provider in the infrastructure page I get a "no longer exist message" and "no records found" message Version-Release number of selected component (if applicable): cfme-5.5.0.13-1.el7cf.x86_64 How reproducible: 100% Steps to Reproduce: 1. navigate to providers -> select provider -> monitoring -> timeline 2. in the results shown (only power results are shown for now) select one of the containers 3. press the provider link in the pop-up window (which has the same name as your openshift provider) Actual results: we are re-directed to the infrastructure page Expected results: we should not be re-directed to the provider page Additional info: screen shots and logs --- Additional comment from Federico Simoncelli on 2015-12-03 12:13:57 EST --- Mooli, this may be related to the balloon changes introduced in: https://github.com/ManageIQ/manageiq/pull/5053 for some reason it seems that the provider link is not correctly generated. Discuss it with Daniel as he is adding the id of the other entities (pods, containers and replicators) and the links generated for those may be wrong as well. --- Additional comment from Mooli Tayer on 2015-12-08 04:16:41 EST --- proposed fix upstream: https://github.com/ManageIQ/manageiq/pull/5742
submitted upstream: https://github.com/ManageIQ/manageiq/pull/5742
verified on cfme-5.5.2.1-1.el7cf.x86_64 The name of the pod is not the same as the provider and when selecting the provider we are getting to the container provider and not the infrastructure provider.
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:0159