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

Upgrading from v3.4.9 to v3.4.10 requires manual action #12144

Closed
invidian opened this issue Jul 17, 2020 · 3 comments · Fixed by kubernetes/kubernetes#94259 or kubernetes/kubernetes#94287

Comments

@invidian
Copy link

After upgrading existing cluster from version v3.4.9 to v.3.4.10, etcd fails to start with following error:

{"level":"fatal","ts":"2020-07-17T07:11:27.596Z","caller":"etcdmain/etcd.go:271","msg":"discovery failed","error":"cannot access data directory: directory \"/theory-controllers-1.etcd\",\"drwxr-xr-x\" exist without desired file permission \
"-rwx------\".","stacktrace":"go.etcd.io/etcd/etcdmain.startEtcdOrProxyV2\n\t/tmp/etcd-release-3.4.10/etcd/release/etcd/etcdmain/etcd.go:271\ngo.etcd.io/etcd/etcdmain.Main\n\t/tmp/etcd-release-3.4.10/etcd/release/etcd/etcdmain/main.go:46\nm
ain.main\n\t/tmp/etcd-release-3.4.10/etcd/release/etcd/main.go:28\nruntime.main\n\t/usr/local/go/src/runtime/proc.go:200"}

To get it to work, manual sudo chmod 0700 execution is required on all members user data directories to get etcd running again. This seems to be a new requirement (or old one, which was not enforced) and it is not mentioned in the changelog nor in the upgrade guide, which was unexpected.

Perhaps this should be documented somewhere?

@tangcong
Copy link
Contributor

@invidian done. previously we only added documentation in 3.5 changelog. thanks.

@spzala
Copy link
Member

spzala commented Jul 17, 2020

@invidian thanks for noticing, we modified the master changelog under #11997 but missed 3.4 and 3.3 while cherry-picking it.

@jingyih
Copy link
Contributor

jingyih commented Aug 26, 2020

For reference, this issue is fixed by #12242

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
4 participants