Change systemd unit files perm to 644

[laozc]

systemd complains about the conf file is not world-inaccessible

Signed-off-by: Zhongcheng Lao [email protected]

[k8s-ci-robot]

Hi @laozc. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

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.

[minikube-bot]

Can one of the admins verify this patch?

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: laozc
To complete the pull request process, please assign sharifelgamal
You can assign the PR to them by writing /assign @sharifelgamal in a comment when ready.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[medyagh]

I am curious is there a related issue you could reference? I like to see the before and after and how this PR would fix the issue

[laozc]

Not sure if there is a pending issue filed for it.
But I saw this when I tried to debug the integration test failure for my other PR.

$ journalctl --no-pager|grep world
Sep 29 14:31:33 gvisor systemd[1]: Configuration file /usr/lib/systemd/system/kubelet.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
Sep 29 14:31:33 gvisor systemd[1]: Configuration file /etc/systemd/system/kubelet.service.d/10-kubeadm.conf is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
Sep 29 14:31:46 gvisor systemd[1]: Configuration file /usr/lib/systemd/system/kubelet.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
Sep 29 14:31:46 gvisor systemd[1]: Configuration file /etc/systemd/system/kubelet.service.d/10-kubeadm.conf is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.

It simply suppresses this systemd warning.

[medyagh]

Not sure if there is a pending issue filed for it.
But I saw this when I tried to debug the integration test failure for my other PR.

$ journalctl --no-pager|grep world
Sep 29 14:31:33 gvisor systemd[1]: Configuration file /usr/lib/systemd/system/kubelet.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
Sep 29 14:31:33 gvisor systemd[1]: Configuration file /etc/systemd/system/kubelet.service.d/10-kubeadm.conf is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
Sep 29 14:31:46 gvisor systemd[1]: Configuration file /usr/lib/systemd/system/kubelet.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
Sep 29 14:31:46 gvisor systemd[1]: Configuration file /etc/systemd/system/kubelet.service.d/10-kubeadm.conf is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.

It simply suppresses this systemd warning.

Thank you for providing the reason, could you verify that after this PR the warning goes away ?

if you could prove me that ! I am okay with this being merged !

[medyagh]

If you could provide me logs that the gvisor warrning goes away after this PR. I approve.

[laozc]

@medyagh You may check the enclosed log (journalctl --no-pager > journalctl.log)
journalctl.log

grep 'world-inaccessible' journalctl.log should give you empty output.

[medyagh]

@minikube-bot OK to test