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

Bug 1699962

Summary: State rollback - Augment CI job with control plane static pod rollback
Product: OpenShift Container Platform Reporter: Scott Dodson <sdodson>
Component: MasterAssignee: Michal Fojtik <mfojtik>
Status: CLOSED NOTABUG QA Contact: Xingxing Xia <xxia>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 4.1.0CC: aos-bugs, jokerman, mmccomas
Target Milestone: ---   
Target Release: 4.1.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: 2019-04-15 16:57:56 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:
Bug Depends On:    
Bug Blocks: 1699952    

Description Scott Dodson 2019-04-15 13:22:02 UTC 
We need to create CI job that is able to verify rollback of cluster state. The proposed flow is as follows.

Master team team to augment CI job with relevant steps below.

Installer - Provision 4.x cluster
MCO       - Edit machine config to write file to /etc/ whose content is “A”
Etcd      - Take etcd backup; capture static pod revision levels
???       - Update release payload
MCO       - Edit machine config to write file to /etc/ whose content is “B”
MCO         Wait for roll-out to complete
Master    - Shutdown kube-apiserver via manual manipulation of static pods on each master
Etcd      - Restore etcd backup
Master    - Restart kube-apiserver via manual manipulation of static pods on each master
MCO       - Wait for cluster to reconcile X period
Master    - All operators report old payload version
MCO       - Ensure on each worker /etc/ content is restored to “A” via MCO

See https://docs.google.com/document/d/1J-Dy_LoIDPqJ9HqI5iGKbzkzNLNy93b3hmHC-YyNfdI/edit?ts=5cad0560#
Comment 1 Scott Dodson 2019-04-15 16:57:56 UTC 
We'll track this via Jira instead.