Wait a while for OpenShift API server to apply last changes#712
Merged
vkmc merged 2 commits intoMay 26, 2026
Merged
Conversation
In some corner cases, when infrastructure might be overloaded, the OpenShift API is not restarted immediately, but it is done after a while. From basic check on failing job, it happens from up to 90 seconds. Making condition that would watch on OpenShift API server that has been finally changed state to to terminating then back to active might be a good alternative here, but can also impact future job if such restart is not needed. Also remove duplicated line from periodic job in zuul config. Signed-off-by: Daniel Pawlik <dpawlik@redhat.com> (cherry picked from commit c656114)
vyzigold
approved these changes
May 21, 2026
Collaborator
|
Seems we need a backport of #713 |
Member
Author
|
Build failed (check pipeline). Post ✔️ stf-crc-ocp_418-local_build SUCCESS in 50m 53s |
Collaborator
|
recheck |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
In some corner cases, when infrastructure might be overloaded, the OpenShift API is not restarted immediately, but it is done after a while. From basic check on failing job, it happens from up to 90 seconds. Making condition that would watch on OpenShift API server that has been finally changed state to to terminating then back to active might be a good alternative here, but can also impact future job if such restart is not needed.
Also remove duplicated line from periodic job in zuul config.
(cherry picked from commit c656114)