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

Bug 1809742

Summary:	All routes, including route for OpenShift Console become unavailable for long time during z-stream upgrade [openshift-4.2.z]
Product:	OpenShift Container Platform	Reporter:	Dan Mace <dmace>
Component:	Networking	Assignee:	Dan Mace <dmace>
Networking sub component:	router	QA Contact:	Hongan Li <hongli>
Status:	CLOSED DUPLICATE	Docs Contact:
Severity:	high
Priority:	unspecified	CC:	aos-bugs
Version:	4.2.z
Target Milestone:	---
Target Release:	4.5.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:	2020-03-31 17:41:09 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:	1809665, 1809668, 1869785
Bug Blocks:

Description Dan Mace 2020-03-03 19:22:55 UTC

This bug was initially created as a copy of Bug #1794169

I am copying this bug because: 



Description of problem:

OpenShift Console becomes unavailable for long time (~30 minutes) during z-stream upgrade of OpenShift Dedicated cluster with 44 nodes (6 master, 2 infra, 36 compute).

Version-Release number of selected component (if applicable):

OCP 4.2.12

How reproducible:


Steps to Reproduce:
1. Setup a OCP cluster with 44 nodes.
2. Start z-stream upgrade.
3. Try accessing cluster console during the upgrade process.

Actual results:

Cluster console is unavailable for ~30 minutes.

Expected results:

Cluster console should be accessible during cluster upgrade.

Additional info:

Without cluster console access, we cannot get cli tokens for OpenShift.

Comment 1 Dan Mace 2020-03-03 19:28:40 UTC

Fix for https://bugzilla.redhat.com/show_bug.cgi?id=1809665 addresses this

Comment 2 Dan Mace 2020-03-31 17:41:09 UTC


*** This bug has been marked as a duplicate of bug 1809665 ***