2042430 – update from 4.7.22 to 4.8.11 is failing due to large amount of secrets to watch

Bug 2042430 - update from 4.7.22 to 4.8.11 is failing due to large amount of secrets to watch

Summary: update from 4.7.22 to 4.8.11 is failing due to large amount of secrets to watch

Keywords:
Status:	CLOSED ERRATA
Alias:	None
Product:	OpenShift Container Platform
Classification:	Red Hat
Component:	OLM
Sub Component:
Version:	4.8
Hardware:	x86_64
OS:	Linux
Priority:	high
Severity:	medium
Target Milestone:	---
Target Release:	4.9.z
Assignee:	Per da Silva
QA Contact:	Jian Zhang
Docs Contact:
URL:
Whiteboard:
Depends On:	2015950
Blocks:
TreeView+	depends on / blocked

Reported:	2022-01-19 14:07 UTC by Scott Dodson
Modified:	2022-01-31 18:23 UTC (History)
CC List:	7 users (show)
Fixed In Version:
Doc Type:	If docs needed, set a value
Doc Text:
Clone Of:	2015950
Environment:
Last Closed:	2022-01-31 18:23:01 UTC
Target Upstream Version:
Embargoed:

Attachments	(Terms of Use)

Links
System	ID	Private	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHBA-2022:0279	0	None	None	None	2022-01-31 18:23:21 UTC

Comment 3 Jian Zhang 2022-01-20 11:32:08 UTC

1, Install an OCP 4.8 cluster.

[cloud-user@preserve-olm-env jian]$ oc get clusterversion
NAME      VERSION   AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.8.28    True        False         14m     Cluster version is 4.8.28

2, Create 1000 fake secrets in openshift-operator-lifecycle-manager project.
[cloud-user@preserve-olm-env jian]$ for i in {1..1000};do oc create secret generic test${i};done
secret/test1 created
secret/test2 created
...

3, Upgrade it to 4.9.z
[cloud-user@preserve-olm-env jian]$ oc adm upgrade --to-image registry.ci.openshift.org/ocp/release:4.9.0-0.nightly-2022-01-20-052841 --force --allow-explicit-upgrade
warning: Using by-tag pull specs is dangerous, and while we still allow it in combination with --force for backward compatibility, it would be much safer to pass a by-digest pull spec instead
warning: The requested upgrade image is not one of the available updates.  You have used --allow-explicit-upgrade to the update to proceed anyway
warning: --force overrides cluster verification of your supplied release image and waives any update precondition failures.
Updating to release image registry.ci.openshift.org/ocp/release:4.9.0-0.nightly-2022-01-20-052841

[cloud-user@preserve-olm-env jian]$ oc get clusterversion
NAME      VERSION   AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.8.28    True        True          73m     Working towards 4.9.0-0.nightly-2022-01-20-052841: 619 of 738 done (83% complete), waiting on machine-config

[cloud-user@preserve-olm-env jian]$ oc get clusterversion
NAME      VERSION                             AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.9.0-0.nightly-2022-01-20-052841   True        False         99s     Cluster version is 4.9.0-0.nightly-2022-01-20-052841

No issue found, upgrading succeed, LGTM, verify it.

Comment 6 errata-xmlrpc 2022-01-31 18:23:01 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 (OpenShift Container Platform 4.9.18 bug fix 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/RHBA-2022:0279

Note You need to log in before you can comment on or make changes to this bug.