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

Bug 1806408

Summary:	Upgrade tests should support multiple iterative versions, report router downtime during upgrade, and be tuned for all platforms
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.3.z	CC:	vlaad
Target Milestone:	---
Target Release:	4.3.z
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1806407	Environment:
Last Closed:	2020-04-08 07:39:51 UTC	Type:	---
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:	1806407
Bug Blocks:

Description Clayton Coleman 2020-02-24 06:42:02 UTC

+++ This bug was initially created as a clone of Bug #1806407 +++

+++ This bug was initially created as a clone of Bug #1806406 +++

A number of improvements have been made to the upgrade tests in 4.5 that must be back ported to earlier releases:

* Allow multiple sequential upgrades to be performed as a unit for 4.1-4.2-4.3-4.4 upgrade testing (https://github.com/openshift/origin/pull/24570)
* Report router downtime (via the console and oauth routes) during upgrade like we do for the core platform and service load balancers (https://github.com/openshift/origin/pull/24580)
* Ensure AWS service LB availability test is tuned consistently with GCP and Azure (https://github.com/openshift/origin/pull/24584)
* Minor interspersed fixes to naming (https://github.com/openshift/origin/pull/24557)

Backport all of these to 4.3 as one unit to avoid future cherry-picking issues.  We need to go back to 4.3 to verify upgrade downtime as fixes are rolled out.

Comment 6 errata-xmlrpc 2020-04-08 07:39:51 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:1262