Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error when reconciling cluster with fixed nodeport #3263

Closed
alenkacz opened this issue Dec 14, 2021 · 1 comment · Fixed by #3268
Closed

Error when reconciling cluster with fixed nodeport #3263

alenkacz opened this issue Dec 14, 2021 · 1 comment · Fixed by #3268
Assignees
Labels
area/k8s kind/bug Something isn't working

Comments

@alenkacz
Copy link
Contributor

Version & Environment

Redpanda version: (use rpk version):
latest operator

What went wrong?

2021-12-14T14:19:38.463Z	ERROR	controller.cluster	Reconciler error	{"reconciler group": "redpanda.vectorized.io", "reconciler kind": "Cluster", "name": "rp-2675372", "namespace": "rp-2-361-949", "error": "unable to create Service resource: Service \"rp-2675372-external\" is invalid: spec.ports[0].nodePort: Invalid value: 31111: provided port is already allocated"}
@alenkacz alenkacz added kind/bug Something isn't working area/k8s labels Dec 14, 2021
@alenkacz alenkacz self-assigned this Dec 14, 2021
@alenkacz
Copy link
Contributor Author

looks like when nodeport service with fixed port get re-created, it does not return AlreadyExists but rather different error :(

➜  temp kubectl apply -f nodeport.yaml
service/my-service created
➜  temp kubectl apply -f nodeport.yaml
service/my-service unchanged
➜  temp kubectl create -f nodeport.yaml
The Service "my-service" is invalid: spec.ports[0].nodePort: Invalid value: 30007: provided port is already allocated

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/k8s kind/bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant