Bug 1701460 - [network-operator] The column of 'FAILING' is nil after the cluster setup
Summary: [network-operator] The column of 'FAILING' is nil after the cluster setup
Keywords:
Status: CLOSED DUPLICATE of bug 1702087
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.1.0
Hardware: All
OS: All
medium
medium
Target Milestone: ---
: 4.1.0
Assignee: Casey Callendrello
QA Contact: zhaozhanqi
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-04-19 06:11 UTC by zhaozhanqi
Modified: 2019-04-23 09:04 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-04-23 09:04:35 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

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 ***
Note You need to log in before you can comment on or make changes to this bug.