Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Increase timeout for all Pods to be eventually ready (elastic#2348)
Some of our E2E tests fail because the CheckExpectedPodsEventuallyReady test reaches its 5min timeout. On good conditions, it takes more than 3 minutes for some rolling upgrades to be completely applied (for eg. TestMutationNodeSetReplacementWithChangeBudget). Depending on external factors (slow Pod scheduling, slow PersistentVolume binding, etc.), we can easily reach the fixed 5min timeout. I propose we increase the timeout to 15min for this particular check. This is an arbitrary value (unfortunately), but I think we're OK with the eventual consistency nature of k8s Pods scheduling. We could make the test smarter (continue waiting if we see there's some small progress), but we'd still have to pick up some arbitrary timeout values anyway, so let's keep things simple.
- Loading branch information