Bug 1696331
| Summary: | [network-operator] Cluster upgrade stuck post network operator redeployment | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Anurag saxena <anusaxen> | ||||||
| Component: | Networking | Assignee: | Casey Callendrello <cdc> | ||||||
| Status: | CLOSED DUPLICATE | QA Contact: | Meng Bo <bmeng> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | medium | ||||||||
| Version: | 4.1.0 | CC: | aos-bugs, danw | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2019-04-04 16:16:15 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: | |||||||||
| Attachments: |
|
||||||||
Created attachment 1551960 [details]
Network operator logs
Yup, dup of 1690747 - thanks for referencing it! *** This bug has been marked as a duplicate of bug 1690747 *** Fix seems good on 4.0.0-0.ci-2019-04-09-225415. Thanks! |
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