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

Bug 2102278

Summary:	Batch timeout calculation is not calculated correctly
Product:	OpenShift Container Platform	Reporter:	Steven Skeard <sskeard>
Component:	Telco Edge	Assignee:	Steven Skeard <sskeard>
Telco Edge sub component:	TALO	QA Contact:	yliu1
Status:	CLOSED ERRATA	Docs Contact:
Severity:	low
Priority:	unspecified	CC:	ijolliff, jun
Version:	4.10	Flags:	sskeard: needinfo+
Target Milestone:	---
Target Release:	4.10.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-07-11 15:28:45 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:

Description Steven Skeard 2022-06-29 14:59:39 UTC

Description of problem:
The batch timeout calculation is incorrect in some situations. For example, in scenarios where most batches finish quickly, there will be plenty of time left in the overall timeout, but later batches that are slow may time out. This was fixed in 4.11 as an enhancement but the 4.10 behaviour is now being considered a bug.

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

How reproducible:
Should be consistently reproducible

Steps to Reproduce:
1. Start a cgu with many batches
2. Observe that all batches always have the same timeout regardless of the time remaining

Actual results:
All cgus get the same timeout calculated based on the original number and original time

Expected results:
Each batch gets a batch timeout calculated based on the remaining batches and remaining time to make maximum use of the provided timeout

Additional info:

Comment 2 yliu1 2022-07-05 18:47:44 UTC

@sskeard could you please set target release as per https://bugzilla.redhat.com/show_bug.cgi?id=2102278#c1? thanks

Comment 4 yliu1 2022-07-06 16:56:48 UTC

Verified with latest 4.10 TALM.
The individual batch timeout now make uses of the total remaining time.

Comment 6 errata-xmlrpc 2022-07-11 15:28:45 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.10.22 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/RHBA-2022:5514