+++ This bug was initially created as a clone of Bug #1758606 +++
Description of problem:
We currently do not comprehensively run a set of disruptive tests against the latest code in any of our branches or against PRs that fits our general pattern for testing.
We should have a test suite "disruptive" as part of openshift-tests that emulates the recovery flow that we document for customers. That previously existed as bash script testing, but should be part of openshift-tests.
We should have an e2e-aws-disruptive test that runs as part of some PRs (installer, machine-config, etcd, origin) and also runs as part of release-informing for 4.3, 4.2, and 4.1. At the end of the test we will reverify the functionality of the cluster.
That suite will in the future add other disruptive events that the cluster must recover from.
Backporting so 4.2 jobs work.
Verification of this needs to happen by a release architect assessing the CI jobs.
--- Additional comment from Clayton Coleman on 2019-10-04 11:30:25 EDT ---
Assigned to etcd because that's the first disruptive test (recovery of etcd) that will be in the suite.
--- Additional comment from errata-xmlrpc on 2019-10-04 14:26:33 EDT ---
Bug report changed to ON_QA status by Errata System.
A QE request has been submitted for advisory RHBA-2019:46256-02
@jforrest, pls help to confirm if the job is ready for 4.2, I can't find it. thanks in advance!