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

Bug 2105992

Summary:	Batch times out faster than configured timeout
Product:	OpenShift Container Platform	Reporter:	Ian Miller <imiller>
Component:	Telco Edge	Assignee:	Steven Skeard <sskeard>
Telco Edge sub component:	TALO	QA Contact:	yliu1
Status:	CLOSED WONTFIX	Docs Contact:
Severity:	high
Priority:	unspecified	CC:	ijolliff, jun, sskeard
Version:	4.10
Target Milestone:	---
Target Release:	4.12.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:	Introduced and fixed in 4.12, no doc update required	Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-04-30 18:04:53 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:	2106102

Description Ian Miller 2022-07-11 13:11:18 UTC

Description of problem:
When applying an OLM operator update to multiple clusters (2 batches total) the first batch times out very quickly even though the timeout is configured as 240 minutes.

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


How reproducible: 100%


Steps to Reproduce:
1. Configure policy for operator update
2. Configure CGU for 2 batches, timeout 240
3. enable CGU

Actual results:


Expected results:


Additional info:

Comment 2 yliu1 2022-07-14 17:51:57 UTC

Set to verified to unblock 4.11 merge. Plus, we can't verify on 4.12 yet. Verification will be done with 4.11.

Comment 3 Rory Thrasher 2024-04-30 18:04:53 UTC

OCP is no longer using Bugzilla and this bug appears to have been left in an orphaned state. If the bug is still relevant, please open a new issue in the OCPBUGS Jira project: https://issues.redhat.com/projects/OCPBUGS/summary