Invalid value: 32443: provided port is already allocated #8237
Unanswered
rangeshgupta-altair
asked this question in
Q&A
Replies: 1 comment 2 replies
-
Just because the chart has been uninstalled doesn't mean that the Kubernetes objects are done deleting. There may be finalizers present that are blocking actual deletion, pending cleanup of other resources. Use |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Environmental Info:
K3s Version: k3s version v1.27.4+k3s1 (36645e7)
HELM Version: Version:"v3.12.2"
Node(s) CPU architecture, OS, and Version:
Linux ip-172-31-2-184 6.2.0-1009-aws #9~22.04.3-Ubuntu SMP Tue Aug 1 21:11:51 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
Cluster Configuration:
Describe the bug:
While reinstalling the service getting the "port is already allocated" error. But after 15-20 mins it works.
After deleting the service, verified that node port is not been used. But still getting "port is already allocated".
Steps To Reproduce:
Expected behavior:
Once the service is deleted. It should be available for reuse immediately
Actual behavior:
After deleting the service I need to wait for 15-20 mins before installing the service again.
Additional context / logs:
Beta Was this translation helpful? Give feedback.
All reactions