[flaky] cdi-uploadproxy-nodeport" provided port is already allocated

[brybacki]

Is this a BUG REPORT or FEATURE REQUEST?:

Uncomment only one, leave it on its own line:

/kind bug

/kind enhancement

What happened:

In the test run https://prow.ci.kubevirt.io/view/gs/kubevirt-prow/pr-logs/pull/kubevirt_containerized-data-importer/1986/pull-containerized-data-importer-e2e-k8s-1.20-upg/1447744882301997056

Cluster did not start cleanly: The Service "cdi-uploadproxy-nodeport" is invalid: spec.ports[0].nodePort: Invalid value: 31001: provided port is already allocated

What you expected to happen:

A port allocated without conflict.

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

Environment:

• CDI version (use kubectl get deployments cdi-deployment -o yaml):
• Kubernetes version (use kubectl version):
• Cloud provider or hardware configuration:
• Install tools:
• Others:

[brybacki]

Similar problem:
istio/istio#14499 (comment)

[akalenyu]

I think I see what's happening, some of our manifests let k8s randomize the nodeport, and maybe that puts
us in a situation where a clash is possible:
https://github.com/kubevirt/containerized-data-importer/blob/main/manifests/templates/imageio.yaml.in#L76-L81
(no nodePort field)
whereas in the uploadproxy-nodeport we are specific:
https://github.com/kubevirt/containerized-data-importer/blob/main/manifests/templates/uploadproxy-nodeport.yaml.in#L15

[kubevirt-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[kubevirt-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle rotten

[kubevirt-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

[kubevirt-bot]

@kubevirt-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

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.