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

[BUG] Old Mount Pod is leak when config is wrong #1172

Closed
zwwhdls opened this issue Nov 11, 2024 · 0 comments · Fixed by #1173
Closed

[BUG] Old Mount Pod is leak when config is wrong #1172

zwwhdls opened this issue Nov 11, 2024 · 0 comments · Fixed by #1173
Assignees
Labels
kind/bug Something isn't working

Comments

@zwwhdls
Copy link
Member

zwwhdls commented Nov 11, 2024

What happened:

  1. Config is wrong and old mount pod won't be ready. Correct the config and CSI Node will recreate a new pod util it is ready
  2. But kubelet will retry while Publish call receives error. And a new Mount Pod will be create it with new config.
  3. Both two mount pods are ready in the cluster, but only the new Mount Pod is in serivce.

What you expected to happen:

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

Anything else we need to know?

Environment:

  • JuiceFS CSI Driver version (which image tag did your CSI Driver use):
  • Kubernetes version (e.g. kubectl version):
  • Object storage (cloud provider and region):
  • Metadata engine info (version, cloud provider managed or self maintained):
  • Network connectivity (JuiceFS to metadata engine, JuiceFS to object storage):
  • Others:
@zwwhdls zwwhdls added the kind/bug Something isn't working label Nov 11, 2024
@zwwhdls zwwhdls self-assigned this Nov 11, 2024
zwwhdls added a commit that referenced this issue Nov 11, 2024
zwwhdls added a commit that referenced this issue Nov 11, 2024
* fix: delete reference in old mount pod when republish, fix #1172

Signed-off-by: zwwhdls <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant