Bug 1696331 - [network-operator] Cluster upgrade stuck post network operator redeployment
Summary: [network-operator] Cluster upgrade stuck post network operator redeployment
Status: CLOSED DUPLICATE of bug 1690747
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.1.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: ---
Assignee: Casey Callendrello
QA Contact: Meng Bo
Depends On:
TreeView+ depends on / blocked
Reported: 2019-04-04 14:43 UTC by Anurag saxena
Modified: 2019-04-11 02:06 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2019-04-04 16:16:15 UTC
Target Upstream Version:

Attachments (Terms of Use)
Cluster version operator logs pertaining to 'network' (32.84 KB, text/plain)
2019-04-04 14:43 UTC, Anurag saxena
no flags Details
Network operator logs (243.85 KB, text/plain)
2019-04-04 14:44 UTC, Anurag saxena
no flags Details

Description Anurag saxena 2019-04-04 14:43:22 UTC
Created attachment 1551923 [details]
Cluster version operator logs pertaining to 'network'

Description of problem: A cluster upgrade via `oc adm` gets stuck post network operator is deleted and redeployed. Observed when 4.0.0-0.nightly-2019-04-02-133735 gets upgraded (or would say downgraded) to 4.0.0-0.nightly-2019-04-02-081046. 

Version-Release number of selected component (if applicable):4.0.0-0.nightly-2019-04-02-133735

How reproducible: Always

Steps to Reproduce:
1. oc delete clusteroperators.config.openshift.io network
2. Wait for network operator to redeployed successfully. Check the cluster network operator status via 

$ oc get clusteroperators.config.openshift.io network
NAME      VERSION                             AVAILABLE   PROGRESSING   FAILING   SINCE
network   4.0.0-0.nightly-2019-04-02-081046   True        False                   3h37m

Noticed the FAILING status reported is empty for indefinite time. Might be a dup of 1690747. Letting dev to evaluate

3. oc adm upgrade --to-image=registry.svc.ci.openshift.org/ocp/release:4.0.0-0.nightly-2019-04-02-081046

Actual results: Upgrade stuck due to network operator doesn't roll out successfully as reported on `oc get clusterversion'
"Unable to apply 4.0.0-0.nightly-2019-04-02-081046: the cluster operator network has not yet successfully rolled out

Expected results: Upgrade should proceed without any issues

Additional info: Step 2 in "Steps to Reproduce" doesn't show any status for 'FAILING' might be blocking the upgrade

Attaching cluster version operator logs (related to network) and network operator pod logs

Comment 1 Anurag saxena 2019-04-04 14:44:44 UTC
Created attachment 1551960 [details]
Network operator logs

Comment 2 Casey Callendrello 2019-04-04 16:16:15 UTC
Yup, dup of 1690747 - thanks for referencing it!

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

Comment 3 Anurag saxena 2019-04-11 02:06:32 UTC
Fix seems good on 4.0.0-0.ci-2019-04-09-225415. Thanks!

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