Bug 1817847

Summary: 4.1 to 4.2 to 4.3 to 4.4 upgrade job fails, one master continuously trying to drain
Product: OpenShift Container Platform Reporter: Clayton Coleman <ccoleman>
Component: Machine Config OperatorAssignee: Antonio Murdaca <amurdaca>
Status: CLOSED DUPLICATE QA Contact: Michael Nguyen <mnguyen>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 4.4   
Target Milestone: ---   
Target Release: 4.4.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-03-27 09:59:08 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 Clayton Coleman 2020-03-27 05:26:25 UTC 
The last segment of upgrade from 4.3 to 4.4 fails because the (first?) never completes:

Mar 26 06:38:42.381 I node/ip-10-0-137-41.ec2.internal Draining node to update config. (48 times)

https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/release-openshift-origin-installer-e2e-aws-upgrade-4.1-to-4.2-to-4.3-to-4.4-nightly/31

The last 10 or so runs have failed.

This is a release blocker for 4.4 until we know why it is happening (could be etcd related too).
Comment 1 Antonio Murdaca 2020-03-27 09:59:08 UTC 
Closing as a dup of the linked one - we're actively working on it and we know 4.3->4.4 works but the changes in the Etcd operator in 4.4 exposed an MCO bug when upgrading from pre-4.3 all the way to 4.4

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