Fix potential port conflict issue with the API server tests by using a random server port if --random-ports is set#6995
Conversation
…ified when running `odo dev` or `odo api-server` This should hopefully fix the potential port conflict flaky issue we are seeing, especially on Windows.
This applies to: - `odo dev --random-ports --api-server --api-server-port=<port>` - `odo api-server --random-ports --port=<port>`
✅ Deploy Preview for odo-docusaurus-preview canceled.
|
|
Skipping CI for Draft Pull Request. |
|
Kudos, SonarCloud Quality Gate passed!
|
--random-ports is set--random-ports is set
Not sure why the pod was not found when trying to start port forwarding. Overriding, but let's keep an eye on this to see if it happens again on some other PRs. /override Kubernetes-Integration-Tests/Kubernetes-Docs-Integration-Tests |
|
@rm3l: Overrode contexts on behalf of rm3l: Kubernetes-Integration-Tests/Kubernetes-Docs-Integration-Tests 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 kubernetes/test-infra repository. |
--random-ports is set--random-ports is set








What type of PR is this:
/area testing
/kind bug
What does this PR do / why we need it:
This lets the OS assign a random ephemeral port to the API Server if
--random-portsis specified when runningodo devorodo api-server.This should hopefully fix the potential port conflict flaky issue we are seeing, especially on Windows.
Which issue(s) this PR fixes:
Fixes #6939
PR acceptance criteria:
Unit test
Integration test
Documentation
How to test changes / Special notes to the reviewer: