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

Bug 1699952

Summary:	We lack CI for control plane state rollback
Product:	OpenShift Container Platform	Reporter:	Scott Dodson <sdodson>
Component:	RFE	Assignee:	Paul Weil <pweil>
Status:	CLOSED NOTABUG	QA Contact:	Xiaoli Tian <xtian>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	4.1.0	CC:	aos-bugs, jokerman, mfojtik, 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:20 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:	1699959, 1699960, 1699962, 1699963
Bug Blocks:

Description Scott Dodson 2019-04-15 13:12:15 UTC

We need to create CI job that is able to verify rollback of cluster state. The proposed flow is as follows

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 2 Scott Dodson 2019-04-15 16:57:20 UTC

We'll track this via Jira instead.