-
Bug
-
Resolution: Done
-
Major
-
None
-
None
-
None
-
False
-
None
-
False
-
-
-
SDN Sprint 249
With 4.15, resource watch completes whenever it is interrupted. But for 4.16 jobs, it does not until 1h grace period kicks in and the job is terminated by ci-operator. This means:
- All 4.16 jobs take 1h longer than normally
- If an upgrade pushes the overall time close to the limit, sub-jobs from aggregator will fail at 4h mark.
This was discovered when investigating this slack thread: https://redhat-internal.slack.com/archives/C01CQA76KMX/p1705578623724259
looking back through recent jobs I cannot find an examples of a 4.16 job timing
out on the resource-watch step. marking this as done. Thanks for the fix kenzhang@redhat.com