From: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH docs 1/2] fix #5140: qdevice SSH access documentation
Date: Thu, 21 Dec 2023 10:29:21 +0100 [thread overview]
Message-ID: <20231221092922.115949-1-f.gruenbichler@proxmox.com> (raw)
rephrase in order to not make it seem like password-based access is required.
Signed-off-by: Fabian Grünbichler <f.gruenbichler@proxmox.com>
---
pvecm.adoc | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/pvecm.adoc b/pvecm.adoc
index 1f78585..03fba9f 100644
--- a/pvecm.adoc
+++ b/pvecm.adoc
@@ -1052,13 +1052,13 @@ pve# pvecm qdevice setup <QDEVICE-IP>
The SSH key from the cluster will be automatically copied to the QDevice.
-NOTE: Make sure that the SSH configuration on your external server allows root
-login via password, if you are asked for a password during this step.
+NOTE: Make sure to setup key-based access for the root user on your external
+server, or temporarily allow root login with password during the setup phase.
If you receive an error such as 'Host key verification failed.' at this
stage, running `pvecm updatecerts` could fix the issue.
-After you enter the password and all the steps have successfully completed, you
-will see "Done". You can verify that the QDevice has been set up with:
+After all the steps have successfully completed, you will see "Done". You can
+verify that the QDevice has been set up with:
----
pve# pvecm status
--
2.39.2
next reply other threads:[~2023-12-21 9:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-21 9:29 Fabian Grünbichler [this message]
2023-12-21 9:29 ` [pve-devel] [PATCH docs 2/2] partially fix #5139: document qnetd port requirement Fabian Grünbichler
2024-02-19 15:34 ` Fiona Ebner
2024-02-20 15:02 ` [pve-devel] applied: " Thomas Lamprecht
2024-02-20 15:01 ` [pve-devel] applied: [PATCH docs 1/2] fix #5140: qdevice SSH access documentation Thomas Lamprecht
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20231221092922.115949-1-f.gruenbichler@proxmox.com \
--to=f.gruenbichler@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox