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.

Sign up for GitHub

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

Jump to bottom

Enhance troubleshooting for SSH key injection #795

Closed
wants to merge 10 commits into from
Closed

Enhance troubleshooting for SSH key injection #795

Changes from 3 commits
Commits
Show all changes
10 commits
Select commit Hold shift + click to select a range
fade1f8
added some more specifics to get ssh working for users which are not …
Dec 5, 2018
d6c5b4b
highlight core as well
Dec 5, 2018
f1cf969
added more specific information around ssh troubleshooting for aws
Dec 6, 2018
5488da0
addressed remaining feedback for troubleshooting of ssh
Jan 2, 2019
e38ad4e
fixed ssh-key to be consistent
Jan 2, 2019
7b7f8eb
removed brackets for ssh-key
Jan 2, 2019
5ef154c
added suggested changes to troubleshoot doc
Jan 2, 2019
268f402
added suggestion and fixed colon and ssh-key
Jan 2, 2019
676d92c
updated command to verify ssh-key and removed line If SSH authenticat…
Jan 3, 2019
c534e54
added fixup! updated command to verify ssh-key and removed line If SS…
Jan 3, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion docs/user/troubleshooting.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -52,7 +52,9 @@ If no pods are shown, etcd will need to be [investigated](#etcd-is-not-running).

### Unable to SSH into Master Nodes

In order to SSH into the master nodes, it is necessary to include an administrator's SSH key during the installation. If SSH authentication is failing, ensure that the proper SSH key is being used.
In order to SSH into the master nodes as user `core`, it is necessary to include an administrator's SSH key during the installation. When asked by the installation wizzard for the ssh-key, make sure you define the absolute path to your key. This key will be added to the core user's authorized_keys file. If installed in aws you will not see this key attached to your instance as a keypair in the aws console.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nits: "ssh" -> "SSH". "SSH" is the protocol; ssh is just the executable. And "core" -> "core" and "authorized_keys" -> "authorized_keys". And "aws" -> "AWS".

Re: "absolute path", the wizard prompt is a Select of your ~/.ssh/*.pub. I don't think it allows free-form input (or at least, it didn't allow it in my tests).

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

minor: "wizzard" -> "wizard"


If SSH authentication is failing, ensure that the proper SSH key is being used.
Copy link
Contributor

@kikisdeliveryservice kikisdeliveryservice Dec 7, 2018 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could we add something like: "Verify your SSH Key by using oc get configmap -n kube-system cluster-config-v1 -o yaml etc... after "ensure that the proper SSH key is being used."? Because I don't think it's clear for people how to verify the key without restarting the install.

Copy link
Contributor

@kikisdeliveryservice kikisdeliveryservice Jan 2, 2019 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I still think we should add something like this to the documentation.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

With the oc get configmap ... and associated lead-in above, I think we can drop this line.


If SSH isn't able to connect to the nodes, they may be waiting on the bootstrap node before they can boot. The initial set of master nodes fetch their boot configuration (the Ignition Config) from the bootstrap node and will not complete until they successfully do so. Check the console output of the nodes to determine if they have successfully booted or if they are waiting for Ignition to fetch the remote config.

Expand Down