OCPBUGS-77493: e2e: Increase GatewayClass acceptance timeout to 5m#1372
Conversation
The 2-minute timeout was set for OSSM 2.x but the OSSM 3.0 installation pipeline takes longer, causing flaky "Waiting for controller" failures. Increase to 5 minutes to accommodate the full Istiod startup chain. Assisted with Claude
📝 WalkthroughWalkthroughA test utility function in the Gateway API test suite was modified to increase the polling timeout for waiting on GatewayClass acceptance. The timeout was extended from 2 minutes to 5 minutes. Explanatory comments were added describing the dependent installation chain (Subscription, OSSM operator, Istio CR, Istiod) that can delay GatewayClass acceptance. The polling interval remains at 2 seconds, and the status checking logic is unchanged. No public API declarations were modified in this change. 🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
/retest |
|
/test e2e-vsphere-static-metallb-operator-gwapi |
|
test worked fine again, I think we can try this and see if flakes reduces /lgtm Thanks @Thealisyed |
|
/retest-required |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: rikatz The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/retest-required |
|
@Thealisyed: This pull request references Jira Issue OCPBUGS-77493, which is invalid:
Comment The bug has been updated to refer to the pull request using the external bug tracker. DetailsIn response to this:
Instructions 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 openshift-eng/jira-lifecycle-plugin repository. |
|
/jira refresh |
|
@rikatz: This pull request references Jira Issue OCPBUGS-77493, which is valid. The bug has been moved to the POST state. 3 validation(s) were run on this bug
No GitHub users were found matching the public email listed for the QA contact in Jira (iamin@redhat.com), skipping review request. DetailsIn response to this:
Instructions 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 openshift-eng/jira-lifecycle-plugin repository. |
|
/test e2e-aws-ovn |
|
/verified by e2e |
|
@rikatz: This PR has been marked as verified by DetailsIn response to this:
Instructions 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 openshift-eng/jira-lifecycle-plugin repository. |
|
/test e2e-hypershift |
|
@Thealisyed I also came to a conclusion that 3 minutes is too short before finding this PR. We should definitely bump to 5 minutes to eliminate slow CCM/api-server/etcd blips in CI. /lgtm |
|
/test e2e-hypershift |
|
/retest TestCreateCluster/ValidateHostedCluster: TestAutoscaling/Teardown:
This is a flaky HyperShift CI infrastructure issue. |
|
/test e2e-hypershift |
|
I have the feeling that this hypershift test is broken. I am considering overriding this right now, given the bug being fixed here will avoid retest of other jobs that are failing today due to Gateway API tests |
|
/test e2e-hypershift |
|
/retest-required |
|
/test hypershift-e2e-aks |
|
/test e2e-gcp-operator |
|
@Thealisyed: all tests passed! 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. |
|
@Thealisyed: Jira Issue Verification Checks: Jira Issue OCPBUGS-77493 Jira Issue OCPBUGS-77493 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓 DetailsIn response to this:
Instructions 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 openshift-eng/jira-lifecycle-plugin repository. |
|
Fix included in accepted release 4.22.0-0.nightly-2026-03-11-034211 |
Summary
assertGatewayClassSuccessfultimeout from 2 minutes to 5 minutesAcceptedcondition is set by Istiod, requiring the full OSSM install pipeline to complete first (Subscription → OLM install → Istio CR → Istiod startup)Test plan
testGatewayAPIObjects🤖 Generated with Claude Code