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

[OLD] Changing from TCP to TCP Proxy doesn't work #2

Open
onitake opened this issue Sep 20, 2019 · 3 comments
Open

[OLD] Changing from TCP to TCP Proxy doesn't work #2

onitake opened this issue Sep 20, 2019 · 3 comments
Milestone

Comments

@onitake
Copy link
Contributor

onitake commented Sep 20, 2019

Moved from: swisstxt/cloudstack-cloud-controller-manager#8

I tried changing from TCP to TCP-Proxy (with annotation).
service.beta.kubernetes.io/cloudstack-load-balancer-proxy-protocol: enabled

Trying this ensuring the loadbalancer failed with:

"Error creating load balancer (will retry): failed to ensure load balancer for service kube-system/traefik-ingress-service: error creating load balancer rule a9a6465af03a211e9886a02001c1a00c-tcp-proxy-80: CloudStack API error 537 (CSExceptionErrorCode: 9999): The range specified, 80-80, conflicts with rule 37282 which has 80-80*

Likely the API Call "create" is called and not "edit".

@onitake
Copy link
Contributor Author

onitake commented Sep 24, 2020

@joschi36 can you test if this bug still occurs? I think we fixed it with all the changes in #9 , but I'm not completely sure.

@joschi36
Copy link
Contributor

No, this is still an issue. I've just verified:
Warning SyncLoadBalancerFailed 9s (x2 over 15s) service-controller Error syncing load balancer: failed to ensure load balancer: error creating load balancer rule a84f70cd744c54e8eb99ebd6c24c7c2b-tcp-proxy-123: CloudStack API error 537 (CSExceptionErrorCode: 9999): The range specified, 123-123, conflicts with rule 68496 which has 123-123

@onitake
Copy link
Contributor Author

onitake commented Apr 29, 2021

I'm not sure how we can address this...
Maybe we should just put a comment in the readme for now.

@weizhouapache weizhouapache added this to the 1.1.0 milestone May 22, 2024
@vishesh92 vishesh92 modified the milestones: 1.1.0, 1.2.0 Jun 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants