Bug 1280354 - Containers: "nil" string is displayed in component status error column
Summary: Containers: "nil" string is displayed in component status error column
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS
Version: 5.5.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: GA
: 5.5.0
Assignee: Daniel Korn
QA Contact: Einat Pacifici
URL:
Whiteboard: container
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-11-11 14:34 UTC by Daniel Korn
Modified: 2015-12-08 13:46 UTC (History)
9 users (show)

Fixed In Version: 5.5.0.11
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-12-08 13:46:24 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2015:2551 0 normal SHIPPED_LIVE Moderate: CFME 5.5.0 bug fixes and enhancement update 2015-12-08 17:58:09 UTC

Description Daniel Korn 2015-11-11 14:34:21 UTC
Description of problem:
When a component status has no errors (condition: type: Healthy, status: True) "nil" string is returned, instead of nil value.

Version-Release number of selected component (if applicable):
cfme-5.5.0.6-beta1.2.1.el7cf.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Add kubernetes/openshift provider
2. Containers -> Providers -> the provider you added
3. look at Component Statuses table -> Healthy == True -> error == "nil"

Actual results:
"nil" is presented

Expected results:
nil value/empty string

Additional info:
upstream issue: https://github.com/ManageIQ/manageiq/issues/5218

Comment 4 Federico Simoncelli 2015-11-30 13:02:36 UTC
This is blocked on the OpenShift issues:

https://github.com/openshift/origin/issues/5865
https://github.com/openshift/origin/issues/3667

which means that it can't be tested until it's resolved there.

Comment 8 errata-xmlrpc 2015-12-08 13:46:24 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/RHSA-2015:2551


Note You need to log in before you can comment on or make changes to this bug.