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

Bug 1699963

Summary: State rollback - Augment CI job with MCO state rollback verification
Product: OpenShift Container Platform Reporter: Scott Dodson <sdodson>
Component: Machine Config OperatorAssignee: Antonio Murdaca <amurdaca>
Status: CLOSED NOTABUG QA Contact: Micah Abbott <miabbott>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 4.1.0   
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:58:06 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:24:20 UTC
We need to augment the state rollback CI job with the items below attributed to MCO team.

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 Antonio Murdaca 2019-04-15 13:27:48 UTC
have instructions for taking etcd backup and restore been published somewhere? we do already have a PR but we can't test it out.

Comment 2 Scott Dodson 2019-04-15 14:40:55 UTC
(In reply to Antonio Murdaca from comment #1)
> have instructions for taking etcd backup and restore been published
> somewhere? we do already have a PR but we can't test it out.

No, not yet, sorry, when filing this I meant to make it clear that this is just a small portion of a larger bug and the smaller bugs will likely be blocked until earlier tasks are complete.

https://bugzilla.redhat.com/show_bug.cgi?id=1699952

Comment 3 Scott Dodson 2019-04-15 16:58:06 UTC
We'll track this via Jira instead.