From fade1f839f7ef0ac0ce35ced4a0701aa5ec6a435 Mon Sep 17 00:00:00 2001 From: Laurent Domb Date: Wed, 5 Dec 2018 16:27:42 -0500 Subject: [PATCH 01/10] added some more specifics to get ssh working for users which are not familiar with coreos --- docs/user/troubleshooting.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/docs/user/troubleshooting.md b/docs/user/troubleshooting.md index 76bff13eeab..d7a894f66e0 100644 --- a/docs/user/troubleshooting.md +++ b/docs/user/troubleshooting.md @@ -52,7 +52,11 @@ 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. This key can be defined in the `install-config.yml` under the variable `sshKey`. The install-config.yml can be generated by running +```sh +openshift-install create install-config +``` +If SSH authentication is failing, ensure that the proper SSH key is being used. 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. From d6c5b4b9d9323c8af0e8a2983da167e05ca2ff29 Mon Sep 17 00:00:00 2001 From: Laurent Domb Date: Wed, 5 Dec 2018 16:29:57 -0500 Subject: [PATCH 02/10] highlight core as well --- docs/user/troubleshooting.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/user/troubleshooting.md b/docs/user/troubleshooting.md index d7a894f66e0..1552cf1bb2b 100644 --- a/docs/user/troubleshooting.md +++ b/docs/user/troubleshooting.md @@ -52,7 +52,7 @@ 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 as user core, it is necessary to include an administrator's SSH key during the installation. This key can be defined in the `install-config.yml` under the variable `sshKey`. The install-config.yml can be generated by running +In order to SSH into the master nodes as user `core`, it is necessary to include an administrator's SSH key during the installation. This key can be defined in the `install-config.yml` under the variable `sshKey`. The install-config.yml can be generated by running ```sh openshift-install create install-config ``` From f1cf96917f44f6ad397dcec6c2ec2874e5e2f58e Mon Sep 17 00:00:00 2001 From: Laurent Domb Date: Thu, 6 Dec 2018 09:54:27 -0500 Subject: [PATCH 03/10] added more specific information around ssh troubleshooting for aws --- docs/user/troubleshooting.md | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/docs/user/troubleshooting.md b/docs/user/troubleshooting.md index 1552cf1bb2b..9f170f3382a 100644 --- a/docs/user/troubleshooting.md +++ b/docs/user/troubleshooting.md @@ -52,10 +52,8 @@ 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 as user `core`, it is necessary to include an administrator's SSH key during the installation. This key can be defined in the `install-config.yml` under the variable `sshKey`. The install-config.yml can be generated by running -```sh -openshift-install create install-config -``` +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. + If SSH authentication is failing, ensure that the proper SSH key is being used. 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. From 5488da0739f30611ffc5e645a523b7f825914850 Mon Sep 17 00:00:00 2001 From: Laurent Domb Date: Wed, 2 Jan 2019 14:18:12 -0500 Subject: [PATCH 04/10] addressed remaining feedback for troubleshooting of ssh --- docs/user/troubleshooting.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/user/troubleshooting.md b/docs/user/troubleshooting.md index 9f170f3382a..da300534838 100644 --- a/docs/user/troubleshooting.md +++ b/docs/user/troubleshooting.md @@ -50,9 +50,9 @@ sudo crictl pods --name=etcd-member If no pods are shown, etcd will need to be [investigated](#etcd-is-not-running). -### Unable to SSH into Master Nodes +### Unable to access the Master Nodes via ssh -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. +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 wizard for the ssh-key, make sure you select your ssh-key from the wizard prompt ( ~/.ssh/*.pub ). 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. If SSH authentication is failing, ensure that the proper SSH key is being used. From e38ad4ec47e6706804d010ed39103a79582e06fe Mon Sep 17 00:00:00 2001 From: Laurent Domb Date: Wed, 2 Jan 2019 14:20:50 -0500 Subject: [PATCH 05/10] fixed ssh-key to be consistent --- docs/user/troubleshooting.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/user/troubleshooting.md b/docs/user/troubleshooting.md index da300534838..9db18e6cff2 100644 --- a/docs/user/troubleshooting.md +++ b/docs/user/troubleshooting.md @@ -50,9 +50,9 @@ sudo crictl pods --name=etcd-member If no pods are shown, etcd will need to be [investigated](#etcd-is-not-running). -### Unable to access the Master Nodes via ssh +### Unable to access the Master Nodes via SSH -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 wizard for the ssh-key, make sure you select your ssh-key from the wizard prompt ( ~/.ssh/*.pub ). 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. +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 wizard for the ssh-key, make sure you select your ssh-key from the wizard prompt ( ~/.ssh/*.pub ). 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. If SSH authentication is failing, ensure that the proper SSH key is being used. From 7b7f8eb65dc0d519643509859480ce99069b6ede Mon Sep 17 00:00:00 2001 From: Laurent Domb Date: Wed, 2 Jan 2019 14:23:32 -0500 Subject: [PATCH 06/10] removed brackets for ssh-key --- docs/user/troubleshooting.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/user/troubleshooting.md b/docs/user/troubleshooting.md index 9db18e6cff2..ee993dedb04 100644 --- a/docs/user/troubleshooting.md +++ b/docs/user/troubleshooting.md @@ -52,7 +52,7 @@ If no pods are shown, etcd will need to be [investigated](#etcd-is-not-running). ### Unable to access the Master Nodes via SSH -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 wizard for the ssh-key, make sure you select your ssh-key from the wizard prompt ( ~/.ssh/*.pub ). 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. +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 wizard for the ssh-key, make sure you select your ssh-key from the wizard prompt **~/.ssh/*.pub**. 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. If SSH authentication is failing, ensure that the proper SSH key is being used. From 5ef154c22d409b9b88f668cdfe82b1be26ebc986 Mon Sep 17 00:00:00 2001 From: Laurent Domb Date: Wed, 2 Jan 2019 16:59:20 -0500 Subject: [PATCH 07/10] added suggested changes to troubleshoot doc --- docs/user/troubleshooting.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/docs/user/troubleshooting.md b/docs/user/troubleshooting.md index ee993dedb04..580bc9ddcbb 100644 --- a/docs/user/troubleshooting.md +++ b/docs/user/troubleshooting.md @@ -52,7 +52,11 @@ If no pods are shown, etcd will need to be [investigated](#etcd-is-not-running). ### Unable to access the Master Nodes via SSH -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 wizard for the ssh-key, make sure you select your ssh-key from the wizard prompt **~/.ssh/*.pub**. 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. +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 wizard for the ssh-key, make sure you select your ssh-key from the wizard prompt `~/.ssh/*.pub`. This key will be added to the `core` user's `authorized_keys` file. The public key is placed in authorized_keys by Ignition and is not configured via platform-specific approaches like [AWS key pairs](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-key-pairs.html). To verify if you added the correct ssh key during installation you can use thefollowing command + +```sh +oc get configmap -n kube-system cluster-config-v1 -o yaml | grep ssh-rsa +``` If SSH authentication is failing, ensure that the proper SSH key is being used. From 268f4026d16d83130fc0a52d771c39708e5413e9 Mon Sep 17 00:00:00 2001 From: Laurent Domb Date: Wed, 2 Jan 2019 17:01:48 -0500 Subject: [PATCH 08/10] added suggestion and fixed colon and ssh-key --- docs/user/troubleshooting.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/user/troubleshooting.md b/docs/user/troubleshooting.md index 580bc9ddcbb..cfaecf483ec 100644 --- a/docs/user/troubleshooting.md +++ b/docs/user/troubleshooting.md @@ -52,7 +52,7 @@ If no pods are shown, etcd will need to be [investigated](#etcd-is-not-running). ### Unable to access the Master Nodes via SSH -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 wizard for the ssh-key, make sure you select your ssh-key from the wizard prompt `~/.ssh/*.pub`. This key will be added to the `core` user's `authorized_keys` file. The public key is placed in authorized_keys by Ignition and is not configured via platform-specific approaches like [AWS key pairs](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-key-pairs.html). To verify if you added the correct ssh key during installation you can use thefollowing command +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 wizard for the ssh-key, make sure you select your ssh-key from the wizard prompt `~/.ssh/*.pub`. This key will be added to the `core` user's `authorized_keys` file. The public key is placed in authorized_keys by Ignition and is not configured via platform-specific approaches like [AWS key pairs](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-key-pairs.html). To verify if you added the correct ssh-key during installation you can use thefollowing command: ```sh oc get configmap -n kube-system cluster-config-v1 -o yaml | grep ssh-rsa From 676d92cc9b20c1cadd55b48f1bd01c51a1665563 Mon Sep 17 00:00:00 2001 From: Laurent Domb Date: Wed, 2 Jan 2019 23:20:28 -0500 Subject: [PATCH 09/10] updated command to verify ssh-key and removed line If SSH authentication is failing ... --- docs/user/troubleshooting.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/docs/user/troubleshooting.md b/docs/user/troubleshooting.md index cfaecf483ec..96beabe3fd1 100644 --- a/docs/user/troubleshooting.md +++ b/docs/user/troubleshooting.md @@ -55,11 +55,9 @@ If no pods are shown, etcd will need to be [investigated](#etcd-is-not-running). 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 wizard for the ssh-key, make sure you select your ssh-key from the wizard prompt `~/.ssh/*.pub`. This key will be added to the `core` user's `authorized_keys` file. The public key is placed in authorized_keys by Ignition and is not configured via platform-specific approaches like [AWS key pairs](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-key-pairs.html). To verify if you added the correct ssh-key during installation you can use thefollowing command: ```sh -oc get configmap -n kube-system cluster-config-v1 -o yaml | grep ssh-rsa +oc get configmap -o "jsonpath={.data['install-config']}" -n kube-system cluster-config-v1 | grep -A1 sshKey ``` -If SSH authentication is failing, ensure that the proper SSH key is being used. - 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. Master nodes waiting for Ignition is indicative of problems on the bootstrap node. SSH into the bootstrap node to [investigate further](#troubleshooting-the-bootstrap-node). From c534e54bf608c10ed3019e83baf917521c447bee Mon Sep 17 00:00:00 2001 From: Laurent Domb Date: Thu, 3 Jan 2019 08:32:23 -0500 Subject: [PATCH 10/10] =?UTF-8?q?added=20fixup!=20updated=20command=20to?= =?UTF-8?q?=20verify=20ssh-key=20and=20removed=20line=20If=20SSH=20auth?= =?UTF-8?q?=E2=80=A6?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- docs/user/troubleshooting.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/user/troubleshooting.md b/docs/user/troubleshooting.md index 96beabe3fd1..7f9e17513ca 100644 --- a/docs/user/troubleshooting.md +++ b/docs/user/troubleshooting.md @@ -50,9 +50,9 @@ sudo crictl pods --name=etcd-member If no pods are shown, etcd will need to be [investigated](#etcd-is-not-running). -### Unable to access the Master Nodes via SSH +### Unable to SSH into Master Nodes -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 wizard for the ssh-key, make sure you select your ssh-key from the wizard prompt `~/.ssh/*.pub`. This key will be added to the `core` user's `authorized_keys` file. The public key is placed in authorized_keys by Ignition and is not configured via platform-specific approaches like [AWS key pairs](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-key-pairs.html). To verify if you added the correct ssh-key during installation you can use thefollowing command: +In order to SSH into the master nodes as user `core`, it is necessary to include an administrator's SSH key during the installation. The selected key, if any, will be added to the `core` user's `~/.ssh/authorized_keys` via [Ignition](https://github.com/coreos/ignition) and is not configured via platform-specific approaches like [AWS key pairs](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-key-pairs.html). You can verify the configured SSH key with: ```sh oc get configmap -o "jsonpath={.data['install-config']}" -n kube-system cluster-config-v1 | grep -A1 sshKey