Red Hat Bugzilla – Bug 1395857
OCP nodes showing as "not ready" in topology view but as "Ready" in Container Node view
Last modified: 2017-02-27 14:23:10 EST
New commit detected on ManageIQ/manageiq/euwe: https://github.com/ManageIQ/manageiq/commit/c3ab503d03ca3ca826411319a91ff1c2317825b0 commit c3ab503d03ca3ca826411319a91ff1c2317825b0 Author: Oleg Barenboim <chessbyte@gmail.com> AuthorDate: Tue Nov 1 15:06:31 2016 -0400 Commit: Satoe Imaishi <simaishi@redhat.com> CommitDate: Wed Jan 4 18:40:33 2017 -0500 Merge pull request #12236 from zeari/topology_condition_status Fix incorrect container node condition status in container topology (cherry picked from commit 8c5d738370681b2bc55718452e3099ef4cc289b0) https://bugzilla.redhat.com/show_bug.cgi?id=1395857 app/services/container_topology_service.rb | 17 +++++++++-------- 1 file changed, 9 insertions(+), 8 deletions(-)
both /container_node/show/1 and container_topology/show show nodes in status Ready. verified on cfme-5.7.1.1-1.el7cf.x86_64
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://rhn.redhat.com/errata/RHSA-2017-0320.html