Bug 2106102
| Summary: | Batch times out faster than configured timeout | |||
|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | OpenShift BugZilla Robot <openshift-bugzilla-robot> | |
| Component: | Telco Edge | Assignee: | Steven Skeard <sskeard> | |
| Telco Edge sub component: | TALO | QA Contact: | yliu1 | |
| Status: | CLOSED ERRATA | Docs Contact: | ||
| Severity: | high | |||
| Priority: | unspecified | CC: | ijolliff, imiller, jun, sskeard | |
| Version: | 4.10 | |||
| Target Milestone: | --- | |||
| Target Release: | 4.11.0 | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | No Doc Update | ||
| Doc Text: |
Introduced and fixed in 4.11, no doc update required
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 2106114 (view as bug list) | Environment: | ||
| Last Closed: | 2022-08-18 04:08:08 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: | 2105992 | |||
| Bug Blocks: | 2106114 | |||
|
Comment 1
yliu1
2022-07-14 17:54:13 UTC
Although the original bug was reported as occuring on a CGU with 2 batches, IMO it can be tested on one spoke. This is important because the test lab only has one spoke. Since the issue is that the timeout was being misinterpreted as seconds instead of minutes then even with just a single batch, it should be verififable. Assuming your CGU uses the default 240 minutes timeout,then if the CGU takes more then 240 seconds to complete and less then 240 minutes and does not time out then it should be considered verified. Could also specify a lower time limit, e.g. timeout: 15, for a short cgu that should not timeout in 15 seconds but will complete in less then 15 minutes. @imiller please correct me if I am wrong Sounds quite reasonable. Test it with a single spoke using a low timeout (eg 15) and confirm the issue is reproduceable. If so you can validate the fix in that environment. Alternatively, if you need an additional cluster to test with two batches I can loan you one. Verified with latest 4.11 TALM brew build. Steps I used with 1 spoke cluster: - created a policy with 2 conflicting CRs, so the policy will never become compliant - create cgu with above policy, and set timeout to 15 (minutes). - verified the cgu timed out after 15 minutes. 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 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:6110 |