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] csi 升级配置修改兼容性问题 #1257

Open
YunhuiChen opened this issue Jan 26, 2025 · 0 comments · May be fixed by #1258
Open

[BUG] csi 升级配置修改兼容性问题 #1257

YunhuiChen opened this issue Jan 26, 2025 · 0 comments · May be fixed by #1258
Labels
kind/bug Something isn't working

Comments

@YunhuiChen
Copy link

What happened:
旧版本 csi 生成的 pod 没有做任何配置修改,仍然会被升级
原因是 旧版的 csi 生成的 mount pod 的配置是 csi 拼成的(有一些信息拿不到),没有记录在 secret 里,然后升级的时候拿拼凑出来的配置和现有的做对比,主要是拿配置 setting 算出一个 hash 做对比,所以会不准。现在新的版本里是把 setting 存在 secret 里,这样每次都是拿上一次生成的配置。
拿旧版本生成的 pod 前两次升级会有这个问题,第三次就固定了
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:
@YunhuiChen YunhuiChen added the kind/bug Something isn't working label Jan 26, 2025
@zwwhdls zwwhdls linked a pull request Jan 26, 2025 that will close this issue
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