Bug 1701460

Summary: [network-operator] The column of 'FAILING' is nil after the cluster setup
Product: OpenShift Container Platform Reporter: zhaozhanqi <zzhao>
Component: NetworkingAssignee: Casey Callendrello <cdc>
Status: CLOSED DUPLICATE QA Contact: zhaozhanqi <zzhao>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.1.0CC: aos-bugs, bbennett
Target Milestone: ---   
Target Release: 4.1.0   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-04-23 09:04:35 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:

Description zhaozhanqi 2019-04-19 06:11:35 UTC 
Description of problem:

setup the cluster with build 4.1.0-0.nightly-2019-04-18-210657, found the FAILING is nil. see:

# oc get co network
NAME      VERSION                             AVAILABLE   PROGRESSING   FAILING   SINCE
network   4.1.0-0.nightly-2019-04-18-210657   True        False                   4h31m

Version-Release number of selected component (if applicable):
4.1.0-0.nightly-2019-04-18-210657

How reproducible:
always

Steps to Reproduce:
1. setup the cluster with the specified version
2. check clusteroperator via `oc get co network`
3.

Actual results:
# oc get co network
NAME      VERSION                             AVAILABLE   PROGRESSING   FAILING   SINCE
network   4.1.0-0.nightly-2019-04-18-210657   True        False                   4h31m

Expected results:

should not be nil for FAILING.

Additional info:
Comment 1 Casey Callendrello 2019-04-23 09:04:35 UTC 
Dupe of 1702087 - the columns have been changed.

*** This bug has been marked as a duplicate of bug 1702087 ***