Fix bert-e waterfall#4964
Conversation
The kube-state-metrics Prometheus job and the generic wait_for_status primitive have been hitting their retry budgets in pre-merge e2e jobs on slower CI runners without any product-level regression — the resources do become healthy, just past the existing timeout. Bump: * tests/post/steps/test_monitoring.py: 30 -> 60 retries (90s -> 180s) for the Prometheus job-up wait. The comment above the call already notes kube-state-metrics can be slow to start. * tests/kube_utils.py: 24 -> 48 retries (120s -> 240s) for the generic wait_for_status used by Volume and other CR tests, and align the inline comment. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Hello teddyandrieux,My role is to assist you with the merge of this Available options
Available commands
Status report is not available. |
Request integration branchesWaiting for integration branch creation to be requested by the user. To request integration branches, please comment on this pull request with the following command: Alternatively, the |
|
/approve |
Integration data createdI have created the integration data for the additional destination branches.
The following branches will NOT be impacted:
You can set option The following options are set: approve |
Waiting for approvalThe following approvals are needed before I can proceed with the merge:
Peer approvals must include at least 1 approval from the following list: The following options are set: approve |
|
LGTM |
|
/bypass_peer_approval |
|
I have successfully merged the changeset of this pull request
The following branches have NOT changed:
Please check the status of the associated issue None. Goodbye teddyandrieux. The following options are set: bypass_peer_approval, approve |
No description provided.