eks-anywhere
eks-anywhere copied to clipboard
Setting the right permission for ssh config
Issue #, if available:
Description of changes: By creating the ssh config file, we should set the correct permission for this file, otherwise, the below error would come up with:
*********************************************************
qemu: fatal: [default]: UNREACHABLE! => {"changed": false, "msg": "Failed to connect to the host via ssh: Bad owner or permissions on /home/image-builder/.ssh/config", "unreachable": true}
qemu:
qemu: PLAY RECAP
Testing (if applicable): Yes Documentation added/planned (if applicable):
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Hi @hitsub2. Thanks for your PR.
I'm waiting for a aws 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.
/lgtm /approve /ok-to-test
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: abhay-krishna
The full list of commands accepted by this bot can be found here.
The pull request process is described here
- ~~docs/OWNERS~~ [abhay-krishna]
Approvers can indicate their approval by writing /approve
in a comment
Approvers can cancel approval by writing /approve cancel
in a comment
/cherrypick release-0.19
@abhay-krishna: new pull request created: #7817
In response to this:
/cherrypick release-0.19
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.