Bug 1708127 - All OCP e2e aws runs failing: timed out waiting for the condition during syncRequiredMachineConfigPools
Summary: All OCP e2e aws runs failing: timed out waiting for the condition during sync...
Keywords:
Status: CLOSED DUPLICATE of bug 1707928
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Machine Config Operator
Version: 4.1.0
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: ---
Assignee: Antonio Murdaca
QA Contact: Micah Abbott
URL:
Whiteboard: buildcop
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-05-09 08:09 UTC by lserven
Modified: 2019-05-09 08:16 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-05-09 08:16:38 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description lserven 2019-05-09 08:09:39 UTC 
Description of problem:
Since May 08 13:42:13 UTC 100% of OCP e2e-aws test runs are failing during installation with the following error:


failed to initialize the cluster: Cluster operator machine-config is reporting a failure: Failed to resync 4.1.0-0.nightly-2019-05-09-041615 because: timed out waiting for the condition during syncRequiredMachineConfigPools: pool master has not progressed to latest configuration: controller version mismatch for rendered-master-0077c73008c536154bc03892e2b78c3e expected 4.1.0-201905081515-dirty has 4.1.0-201905081412-dirty, retrying: timed out waiting for the condition"

example: https://openshift-gce-devel.appspot.com/build/origin-ci-test/logs/release-openshift-ocp-installer-e2e-aws-4.1/179

How reproducible:
100% since May 08 13:42:13 UTC
Comment 1 lserven 2019-05-09 08:16:38 UTC 

*** This bug has been marked as a duplicate of bug 1707928 ***
Note You need to log in before you can comment on or make changes to this bug.