Skip to content

LB reappeared after service was deleted #166

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

Closed
alapidas opened this issue Apr 2, 2018 · 4 comments
Closed

LB reappeared after service was deleted #166

alapidas opened this issue Apr 2, 2018 · 4 comments

Comments

@alapidas
Copy link
Contributor

alapidas commented Apr 2, 2018

I saw this at this same time I saw #165 - after a few minutes, it looks like CCM recreated a LB for a service that I deleted. The service did not reappear, but the LB got recreated for some reason (relevant logs in #165)

@alapidas alapidas added the bug label Apr 2, 2018
@prydie
Copy link
Contributor

prydie commented Apr 4, 2018

I see from the logs in #165 that you aren't running the latest version of the CCM. Would you mind upgrading and seeing if you continue to see the problem?

@prydie prydie removed the bug label Apr 5, 2018
@jhorwit2
Copy link
Member

jhorwit2 commented Apr 6, 2018

@alapidas this sounds like an upstream problem. We have no control over when the underlying core code calls the CCM to create/update/delete load balancers. You may have ran into a bug that'll be fixed once my upstream PR is merged / released. kubernetes/kubernetes#54569

@jhorwit2
Copy link
Member

jhorwit2 commented Apr 6, 2018

@prydie what was your fix before? #165 has no corresponding commit/pr.

@alapidas
Copy link
Contributor Author

alapidas commented Apr 6, 2018

#166 (comment)

We've updated and will reopen this ticket if I can repro.

@alapidas alapidas closed this as completed Apr 6, 2018
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

3 participants