Bug 1388971 - Container Topology Nodes appear as "Not Ready"
Summary: Container Topology Nodes appear as "Not Ready"
Keywords:
Status: CLOSED DUPLICATE of bug 1387273
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS
Version: 5.7.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: GA
: cfme-future
Assignee: Ari Zellner
QA Contact: Dave Johnson
URL:
Whiteboard: container
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-26 15:20 UTC by Matt Bagnara
Modified: 2016-11-01 04:38 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-10-27 08:27:39 UTC
Category: ---
Cloudforms Team: Container Management
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

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 ***
Note You need to log in before you can comment on or make changes to this bug.