Bug 1285610 - Containers Overview page shows provider count as 0 even when providers are added
Summary: Containers Overview page shows provider count as 0 even when providers are added
Keywords:
Status: CLOSED DUPLICATE of bug 1283564
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS
Version: 5.5.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: GA
: 5.5.0
Assignee: Alissa
QA Contact: Dave Johnson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-11-26 03:56 UTC by Nandini Chandra
Modified: 2015-12-01 10:46 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-12-01 10:46:36 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
screen shot of containers overview page (35.26 KB, image/png)
2015-11-26 03:56 UTC, Nandini Chandra 		no flags Details
View All

Description Nandini Chandra 2015-11-26 03:56:17 UTC 
Created attachment 1099093 [details]
screen shot of containers overview page

Description of problem:
-----------------------
My appliance is managing an Openshift provider.However,the Containers Overview page shows 0 providers.The count of other entities such as nodes,containers is correctly displayed.


Version-Release number of selected component (if applicable):
-----------------------------------------------------------
5.5.0.12


How reproducible:
-----------------
Always


Steps to Reproduce:
-------------------
1.
2.
3.


Actual results:
--------------


Expected results:
----------------


Additional info:
----------------
Comment 2 Alissa 2015-12-01 08:01:24 UTC 
Ari, is this duplicate of this bug?
https://bugzilla.redhat.com/show_bug.cgi?id=1283564
Comment 3 Ari Zellner 2015-12-01 10:45:53 UTC 
Looks like it. The fix for it is up in gitlab - merge request #548
Comment 4 Alissa 2015-12-01 10:46:36 UTC 

*** This bug has been marked as a duplicate of bug 1283564 ***
Note You need to log in before you can comment on or make changes to this bug.