Bug 1972829

Summary:	Upgrade tests should fail when ingress is disrupted
Product:	OpenShift Container Platform	Reporter:	Clayton Coleman <ccoleman>
Component:	Networking	Assignee:	Miciah Dashiel Butler Masters <mmasters>
Networking sub component:	router	QA Contact:	Hongan Li <hongli>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	high
Priority:	medium	CC:	aos-bugs, mmasters
Version:	4.9
Target Milestone:	---
Target Release:	4.9.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1972896 (view as bug list)		Environment:
Last Closed:	2021-10-18 17:34:57 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:	1972896

Description Clayton Coleman 2021-06-16 17:19:59 UTC

Now that 4.8 has resolved router outages due to LocalTrafficPolicy, we can tighten the testing so that we don't regress. Add the same logic that control plane has to make upgrade non-disruptive for ingress.

Comment 2 Hongan Li 2021-07-13 04:42:46 UTC

checked upgrade ci and "disruption_tests: [sig-network-edge] Cluster frontend ingress remain available" is passed.

see: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-release-master-ci-4.9-e2e-aws-upgrade/1414662256355971072

Comment 5 errata-xmlrpc 2021-10-18 17:34:57 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 (Moderate: OpenShift Container Platform 4.9.0 bug fix and security update), 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/RHSA-2021:3759