Setup correct permissions for etcd config dir, fixes #10289 #10291
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: morsik If they are not already assigned, you can assign the PR to them by writing The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
openshift-ci-robot
added
the
size/XS
|
Hi @morsik. Thanks for your PR. I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
openshift-ci-robot
added
the
needs-ok-to-test
morsik
changed the title
|
Can one of the admins verify this patch?
|
| @@ -145,6 +145,8 @@ | |||
| unarchive: | |||
| src: "/tmp/{{ inventory_hostname }}/{{ etcd_generated_certs_dir }}/{{ etcd_cert_subdir }}.tgz" | |||
| dest: "{{ etcd_cert_config_dir }}" | |||
| owner: etcd | |||
There was a problem hiding this comment.
Why is it necessary? Tarball should preserve permissions set on etcd_ca_host
There was a problem hiding this comment.
You tell me ;)
Without this it restores file owner/group with root:root which makes etcd fail to read it's configuration.
There was a problem hiding this comment.
Does etcd_ca_host has these set with root:root? What's you config - standalone etcd or static pods?
There was a problem hiding this comment.
@vrutkovs: I tried manually set etcd:etcd (using chown -R etcd:etcd /etc/etcd) but Ansible later sets it to root:root anyway with this task. I tried also reinstalling etcd.
This is fresh cluster installed yestarday, and yestarday I issued redeploy_certificates which broke whole cluster cause of this problem.
|
Master branch is closed! A major refactor is ongoing in devel-40. Changes for 3.x should be made directly to the latest release branch they're relevant to and backported from there. |
See #10289
Putting this into
masterbranch. Will need to backport that torelease-3.11andrelease-3.10too.After changing this and rerunning
redeploy_certificatesmy cluster is back again.