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

Bug 2109667

Summary:	Install plan approval for operator upgrade takes more than 5 minutes
Product:	OpenShift Container Platform	Reporter:	OpenShift BugZilla Robot <openshift-bugzilla-robot>
Component:	Telco Edge	Assignee:	jun
Telco Edge sub component:	TALO	QA Contact:	yliu1
Status:	CLOSED ERRATA	Docs Contact:
Severity:	medium
Priority:	medium	CC:	ijolliff, jun, keyoung
Version:	4.10
Target Milestone:	---
Target Release:	4.11.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:	2022-12-01 18:58:21 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:	2106101
Bug Blocks:

Description OpenShift BugZilla Robot 2022-07-21 18:30:10 UTC

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

Description of problem:
The subscription status sometimes takes a bit longer to reach "upgrade pending" for TALM to create MCA and approve the install plan. Currently TALM checks subscription status every 5 minutes.

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


How reproducible:
50%

Steps to Reproduce:
1. 
2.
3.

Actual results:


Expected results:
TALM should check more often when waiting for this as it typically does not take longer than 5 minutes.

Additional info:

Comment 1 yliu1 2022-10-25 23:41:15 UTC

installplans now gets approved in about 1 minute using latest 4.11.2 TALM.

Comment 4 errata-xmlrpc 2022-12-01 18:58:21 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.11.16 CNF vRAN extras 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/RHEA-2022:8690