Bug 1292436

Summary: Containers dashboard - Kubernetes provider count should not be available in containers dashboard
Product: Red Hat CloudForms Management Engine Reporter: John Prause <jprause>
Component: UI - OPSAssignee: Ari Zellner <azellner>
Status: CLOSED ERRATA QA Contact: Avi Tal <atal>
Severity: high Docs Contact:
Priority: unspecified    
Version: 5.6.0CC: atal, azellner, bazulay, cpelland, fsimonce, gblomqui, hkataria, jhardy, mfeifer, mpovolny, obarenbo, pkovar, srevivo
Target Milestone: GAKeywords: ZStream
Target Release: 5.5.2   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: container
Fixed In Version: 5.5.2.1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1290383 Environment:
Last Closed: 2016-02-10 15:29:07 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1290383    
Bug Blocks:    

Description John Prause 2015-12-17 12:51:56 UTC 
+++ This bug was initially created as a clone of Bug #1290383 +++

Description of problem:
The kubernetes icon shows up though the user cant insert a kubernetes provider

Steps to Reproduce:
1. go to containers->Overview

--- Additional comment from Ari Zellner on 2015-12-10 06:39:24 EST ---

I'm unable to assign this bug to myself
The fix is up on github: https://github.com/ManageIQ/manageiq/pull/5781
Comment 4 Ari Zellner 2016-01-04 12:06:46 UTC 
upstream PR: https://github.com/ManageIQ/manageiq/pull/5781(merged)
Comment 6 Ari Zellner 2016-01-07 13:45:22 UTC 
http://gitlab.cloudforms.lab.eng.rdu2.redhat.com/cloudforms/cfme/merge_requests/680
Comment 8 Avi Tal 2016-01-18 17:37:06 UTC 
Ari, How would i reproduce it in downstream if we do not support K8S in downstream?
Comment 9 Avi Tal 2016-01-20 23:10:08 UTC 
cfme 5.5.2.1
No K8S provider icon in dashboard
Comment 10 errata-xmlrpc 2016-02-10 15:29:07 UTC 
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