Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1280354 - Containers: "nil" string is displayed in component status error column
Containers: "nil" string is displayed in component status error column
Status: CLOSED ERRATA
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS (Show other bugs)
5.5.0
Unspecified Unspecified
medium Severity medium
: GA
: 5.5.0
Assigned To: Daniel Korn
Einat Pacifici
container
: OtherQA
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-11-11 09:34 EST by Daniel Korn
Modified: 2015-12-08 08:46 EST (History)
9 users (show)

See Also:
Fixed In Version: 5.5.0.11
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-12-08 08:46:24 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2015:2551 normal SHIPPED_LIVE Moderate: CFME 5.5.0 bug fixes and enhancement update 2015-12-08 12:58:09 EST

  None (edit)
Description Daniel Korn 2015-11-11 09:34:21 EST
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 08:02:36 EST
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 08:46:24 EST
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.