fix(install): increase WaitUntilAvailable timeout from 5m to 10m - #9306
fix(install): increase WaitUntilAvailable timeout from 5m to 10m#9306apahim wants to merge 1 commit into
Conversation
On GKE Autopilot clusters, the operator deployment may take longer than 5 minutes to roll out because Autopilot needs to scale up nodes before pods can be scheduled. This causes the hypershift install --wait-until-available flag to fail with a context deadline exceeded error. Increase the timeout to 10 minutes to accommodate Autopilot cold start scheduling latency. Signed-off-by: Amador Pahim <apahim@redhat.com> Commit-Message-Assisted-by: Claude (via Claude Code)
|
Pipeline controller notification For optional jobs, comment This repository is configured in: LGTM mode |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository YAML (base), Central YAML (inherited) Review profile: CHILL Plan: Enterprise Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthrough
Suggested reviewers: Mergeability Score: ⚪ Minimal · up to The install wait timeout increases from 5 to 10 minutes to accommodate slower cluster scheduling while returning immediately when the deployment is ready; no actionable merge-blocking risk remains. 🚥 Pre-merge checks | ✅ 11✅ Passed checks (11 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: apahim The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #9306 +/- ##
=======================================
Coverage 45.75% 45.75%
=======================================
Files 781 781
Lines 97837 97837
=======================================
Hits 44761 44761
Misses 50007 50007
Partials 3069 3069
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
|
/lgtm |
|
Scheduling tests matching the |
Test Resultse2e-aws
e2e-aks
|
|
@apahim: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
|
/rebase |
|
🤖 Rebasing PR onto main: workflow run |
|
|
|
/rebase |
|
🤖 Rebasing PR onto main: workflow run |
|
|
Problem
On GKE Autopilot clusters, the HyperShift operator deployment may take longer than 5 minutes to roll out because Autopilot needs to scale up nodes before pods can be scheduled. This causes
hypershift install --wait-until-availableto fail with:This is one of the root causes of the
e2e-v2-gkeCI flakiness:https://prow.ci.openshift.org/job-history/gs/test-platform-results/pr-logs/directory/pull-ci-openshift-hypershift-main-e2e-v2-gke
Fix
Increase the
WaitUntilAvailablecontext timeout from 5 minutes to 10 minutes incmd/install/install.go. This accommodates GKE Autopilot cold-start scheduling latency without affecting non-Autopilot environments (the wait returns as soon as the deployment is available).Related
Summary by CodeRabbit