You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be naturally consistent with "ssh", "ssh-copy-id", etc. That means as long as SSH_AUTH_SOCK gets detected, --use-ssh-agent is automatically enabled. We can add code to enforce --use-ssh-agent no if really need to use the local ssh key.
Use --use-ssh-agent to tell crmsh we want to enable ssh-agent
If we don't use --use-ssh-agent option, local ssh key will be created and used:
adm@alp-1:~> sudo -E crm cluster init -ys /dev/sda9 -N adm@alp-2
INFO: Loading "default" profile from /etc/crm/profiles.yml
INFO: Loading "knet-default" profile from /etc/crm/profiles.yml
WARNING: $SSH_AUTH_SOCK is detected. As a tip, using the --use-ssh-agent option could avoid generate local root ssh keys on cluster nodes.
INFO: A new ssh keypair is generated for user adm.
INFO: A new ssh keypair is generated for user hacluster.
Here is the current oneliner:
adm@tw-1:~> sudo -E crm cluster init --use-ssh-agent -ys /dev/disk/by-partlabel/sbd -N $USER@tw-2
It would be naturally consistent with "ssh", "ssh-copy-id", etc. That means as long as SSH_AUTH_SOCK gets detected, --use-ssh-agent is automatically enabled. We can add code to enforce
--use-ssh-agent no
if really need to use the local ssh key.adm@tw-1:~> sudo -E crm cluster init -ys /dev/disk/by-partlabel/sbd -N $USER@tw-2
The text was updated successfully, but these errors were encountered: