Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1887055

Summary: upgrade from 4.5.14 to 4.6.0-0.nightly-2020-10-09-033719, machine-config is degraded
Product: OpenShift Container Platform Reporter: Junqi Zhao <juzhao>
Component: Machine Config OperatorAssignee: Antonio Murdaca <amurdaca>
Status: CLOSED DUPLICATE QA Contact: Michael Nguyen <mnguyen>
Severity: high Docs Contact:
Priority: high    
Version: 4.6CC: trozet, yanyang
Target Milestone: ---   
Target Release: 4.6.0   
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: 2020-10-12 20:53:44 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 Junqi Zhao 2020-10-10 12:13:48 UTC
Description of problem:
IPI on AWS & FIPS on & OVN cluster, upgrade from 4.5.14 to 4.6.0-0.nightly-2020-10-09-033719, machine-config is degraded
Spec:
Status:
Conditions:
  Last Transition Time:  2020-10-09T08:26:36Z
  Message:               Working towards 4.6.0-0.nightly-2020-10-09-033719
  Status:                True
  Type:                  Progressing
  Last Transition Time:  2020-10-09T08:40:44Z
  Message:               Unable to apply 4.6.0-0.nightly-2020-10-09-033719: timed out waiting for the condition during syncRequiredMachineConfigPools: pool master has not progressed to latest configuration: controller version mismatch for rendered-master-4f3802fd59c79bf7fe372a24421eb65f expected 48d52f385642cbecf5c95e0ac4b0ec8c37664fe7 has 13dd7810adc20c7e6d99adc4179969eac54e7783: 0 (ready 0) out of 3 nodes are updating to latest configuration rendered-master-50213bc16fc94eab9773bdbf66861001, retrying
  Reason:                RequiredPoolsFailed
  Status:                True
  Type:                  Degraded
  Last Transition Time:  2020-10-09T08:24:31Z
  Message:               Cluster not available for 4.6.0-0.nightly-2020-10-09-033719
  Status:                False
  Type:                  Available
  Last Transition Time:  2020-10-09T06:25:09Z
  Reason:                AsExpected
  Status:                True
  Type:                  Upgradeable
Extension:
  Last Sync Error:  pool master has not progressed to latest configuration: controller version mismatch for rendered-master-4f3802fd59c79bf7fe372a24421eb65f expected 48d52f385642cbecf5c95e0ac4b0ec8c37664fe7 has 13dd7810adc20c7e6d99adc4179969eac54e7783: 0 (ready 0) out of 3 nodes are updating to latest configuration rendered-master-50213bc16fc94eab9773bdbf66861001, retrying
  Master:           0 (ready 0) out of 3 nodes are updating to latest configuration rendered-master-50213bc16fc94eab9773bdbf66861001
  Worker:           all 3 nodes are at latest configuration rendered-worker-1332ccf48fb3a03b8dea8157cebc9c18
Related Objects:

Version-Release number of selected component (if applicable):
IPI on AWS & FIPS on & OVN cluster, upgrade from 4.5.14 to 4.6.0-0.nightly-2020-10-09-033719

How reproducible:
Always

Steps to Reproduce:
1. IPI on AWS & FIPS on & OVN cluster, upgrade from 4.5.14 to 4.6.0-0.nightly-2020-10-09-033719
2.
3.

Actual results:
machine-config is degraded

Expected results:


Additional info:

Comment 1 Junqi Zhao 2020-10-10 12:14:35 UTC
maybe caused by OVN, see bug 1880591

Comment 3 Tim Rozet 2020-10-12 20:52:17 UTC
This looks like it is the same bug as 1880591:

2020-10-09T08:05:37.20360662Z 2020-10-09T08:05:37Z|00078|binding|WARN|localnet port '' already set for datapath '12', skipping the new port 'br-local_ip-10-0-159-59.us-east-2.compute.internal'.
2020-10-09T08:06:11.106115022Z 2020-10-09T08:06:11Z|00079|binding|WARN|localnet port '' already set for datapath '12', skipping the new port 'br-local_ip-10-0-159-59.us-east-2.compute.internal'.

Comment 4 Tim Rozet 2020-10-12 20:53:44 UTC

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