Bug 1388971

Summary:	Container Topology Nodes appear as "Not Ready"
Product:	Red Hat CloudForms Management Engine	Reporter:	Matt Bagnara <mbagnara>
Component:	UI - OPS	Assignee:	Ari Zellner <azellner>
Status:	CLOSED DUPLICATE	QA Contact:	Dave Johnson <dajohnso>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	5.7.0	CC:	fsimonce, hkataria, jhardy, mpovolny, obarenbo
Target Milestone:	GA
Target Release:	cfme-future
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	container
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-10-27 08:27:39 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	Container Management	Target Upstream Version:
Embargoed:

Description Matt Bagnara 2016-10-26 15:20:58 UTC

Description of problem:
When you mouse over container topology nodes, the status appears as "Not Ready", despite actual KubeletReady state.

Version-Release number of selected component (if applicable):
5.7.0.7-beta1.20161025153249_9376fbd

How reproducible:
Configure a container provider using OpenShift that has a running state.


Steps to Reproduce:
1. Select compute->containers->topology
2. Mouse over one of the available OCP nodes.


Actual results:

Status field says "Not Ready"

Expected results:
Expected status should be displayed.


Additional info:

Comment 2 Harpreet Kataria 2016-10-26 19:38:38 UTC

Federico,

Can you please take a look.

Thanks,
~Harpreet

Comment 3 Federico Simoncelli 2016-10-27 08:27:39 UTC

Matt I think this is a duplicate of bug 1387273
Feel free to reopen if you think otherwise.

*** This bug has been marked as a duplicate of bug 1387273 ***