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

Bug 1805457

Summary:	There should be a CI test suite for upgrading across multiple versions
Product:	OpenShift Container Platform	Reporter:	Clayton Coleman <ccoleman>
Component:	Test Infrastructure	Assignee:	Clayton Coleman <ccoleman>
Status:	CLOSED ERRATA	QA Contact:
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	4.5	CC:	skuznets
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:
Clones:	1805459 (view as bug list)		Environment:
Last Closed:	2020-05-04 11:38:25 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:	1805459

Description Clayton Coleman 2020-02-20 20:08:56 UTC

In 4.3 we found a serious bug that only existed when upgrading a cluster from 4.1 to 4.2 to 4.3.  We should have an e2e test that verifies these upgrade paths.

Create a test that performs sequential upgrades and backport to 4.3 and 4.4 so we can create the jobs.  The jobs will select a representative build from each stream, and perform tests as we upgrade, and then at the very end we will run the e2e suite to ensure the cluster is fully functional.

Comment 1 Clayton Coleman 2020-03-17 17:41:59 UTC

Jobs are https://prow.svc.ci.openshift.org/job-history/origin-ci-test/logs/release-openshift-origin-installer-e2e-aws-upgrade-4.1-to-4.2-to-4.3-to-4.4-nightly and https://prow.svc.ci.openshift.org/job-history/origin-ci-test/logs/release-openshift-origin-installer-e2e-aws-upgrade-4.2-to-4.3-to-4.4-to-4.5-ci

They run periodically.  We will add others over time.

Comment 4 errata-xmlrpc 2020-05-04 11:38:25 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:0581