Bug 1826680

Summary: non-existed service should display None same as the other empty fields on operator instance page
Product: OpenShift Container Platform Reporter: XiaochuanWang <xiaocwan>
Component: Management ConsoleAssignee: Robb Hamilton <rhamilto>
Status: CLOSED ERRATA QA Contact: Yadan Pei <yapei>
Severity: low Docs Contact:
Priority: medium    
Version: 4.5CC: aos-bugs, jokerman, rhamilto
Target Milestone: ---   
Target Release: 4.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of:
: 1827766 (view as bug list) Environment:
Last Closed: 2020-07-13 17:30:08 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:    
Bug Blocks: 1827766    
Attachments:
Description Flags
screenshot for the issue none

Description XiaochuanWang 2020-04-22 10:17:57 UTC
Created attachment 1680800 [details]
screenshot for the issue

Description of problem:
After user installed an operator and created instance, if there is no Service created, the field should display None just as the other empty fields

Version-Release number of selected component (if applicable):
4.5.0-0.nightly-2020-04-21-103613

How reproducible:
Always

Steps to Reproduce:
1.User installed an operator such as Etcd, and created instance such as EtcdCluster
2.Check the detail page of EtcdCluster.
url: k8s/ns/prozyp/clusterserviceversions/etcdoperator.v0.9.4/etcd.database.coreos.com~v1beta2~EtcdCluster/example/


Actual results:
2. The Service field has an icon and display empty as service name

Expected results:
2. Service field should display None which is same as the other empty fields.

Additional info:

Comment 3 XiaochuanWang 2020-04-27 03:01:07 UTC
Now the Service empty value displays "None" as expected.
Verified on 4.5.0-0.nightly-2020-04-26-203839

Comment 4 errata-xmlrpc 2020-07-13 17:30:08 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-2020:2409