Skip to content
This repository has been archived by the owner on Jan 9, 2023. It is now read-only.

Better explain incorrect keyfile permissions #170

Open
charlieegan3 opened this issue Apr 17, 2018 · 2 comments · May be fixed by #355
Open

Better explain incorrect keyfile permissions #170

charlieegan3 opened this issue Apr 17, 2018 · 2 comments · May be fixed by #355
Assignees
@JoshVanL
Labels
kind/bug Categorizes issue or PR as related to a bug. kind/feature Categorizes issue or PR as related to a new feature.

Comments

@charlieegan3
Copy link
Contributor

charlieegan3 commented Apr 17, 2018 •
edited

Is this a BUG REPORT or FEATURE REQUEST?:

/kind feature

What happened:
When running tarmak apply, if the ssh keys have the incorrect permissions, then the apply command fails when connecting to the bastion and spends a long time without a useful error message.

DEBU[0017] check SSH connection to bastion cmd=[ssh -F dev-hub/ssh_config -N bastion /bin/true]  app=tarmak destination=vault-3.tarmak.local                                                  
DEBU[0017] check SSH connection to bastion cmd=[ssh -F dev-hub/ssh_config -N bastion /bin/true]  app=tarmak destination=vault-1.tarmak.local                                                  
DEBU[0017] check SSH connection to bastion cmd=[ssh -F dev-hub/ssh_config -N bastion /bin/true]  app=tarmak destination=vault-2.tarmak.local                                                  
WARN[0017] error checking SSH connecting to bastion: exit status 255  app=tarmak cluster=hub environment=dev stack=vault                                                                      
WARN[0017] error checking SSH connecting to bastion: exit status 255  app=tarmak cluster=hub environment=dev stack=vault                                                                      
WARN[0017] error checking SSH connecting to bastion: exit status 255  app=tarmak cluster=hub environment=dev stack=vault

What you expected to happen:
This is caused by the permissions being incorrect on the ssh key files. I'd expect tarmak to explain this in an error.

How to reproduce it (as minimally and precisely as possible):
Set the permissions on the id_rsa files to something wide open and run cluster apply.

Anything else we need to know?:
This is worth fixing as it's an issue with our tarmak-config using git-crypt repo pattern.
@jetstack-bot jetstack-bot added the kind/bug Categorizes issue or PR as related to a bug. label Apr 17, 2018
@charlieegan3
Copy link
Contributor Author

/kind feature

@jetstack-bot jetstack-bot added the kind/feature Categorizes issue or PR as related to a new feature. label Apr 17, 2018
@JoshVanL
Copy link
Contributor

/assign

@JoshVanL JoshVanL linked a pull request Jun 29, 2018 that will close this issue
Open
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@JoshVanL JoshVanL

Labels
kind/bug Categorizes issue or PR as related to a bug. kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

File permissions validations JoshVanL/tarmak
3 participants
@charlieegan3 @JoshVanL @jetstack-bot