fix: enable variable expansion in cluster node SSH key heredoc
Changed heredoc delimiter from <<'EOF' to <<EOF to allow bash variable expansion. Previously $SSH_PUBLIC_KEY and $SSH_RESTRICTED_KEY_ENTRY were being passed as literal strings instead of their actual values, so cluster nodes never received the correct SSH keys. This fixes cluster node ProxyJump setup - now both restricted and unrestricted keys are properly added to cluster nodes.
This commit is contained in:
parent
c17059ca8e
commit
21712111e7
1 changed files with 1 additions and 1 deletions
|
|
@ -4058,7 +4058,7 @@ if [ "$TEMPERATURE_ENABLED" = true ] && command -v pvecm >/dev/null 2>&1 && comm
|
||||||
if [[ $REMOTE_REPLY =~ ^[Yy]$ ]]; then
|
if [[ $REMOTE_REPLY =~ ^[Yy]$ ]]; then
|
||||||
for NODE in "${OTHER_NODES_LIST[@]}"; do
|
for NODE in "${OTHER_NODES_LIST[@]}"; do
|
||||||
echo "Configuring temperature monitoring on $NODE..."
|
echo "Configuring temperature monitoring on $NODE..."
|
||||||
if ssh -o BatchMode=yes -o StrictHostKeyChecking=no -o ConnectTimeout=5 -o LogLevel=ERROR root@"$NODE" "bash -s" <<'EOF'
|
if ssh -o BatchMode=yes -o StrictHostKeyChecking=no -o ConnectTimeout=5 -o LogLevel=ERROR root@"$NODE" "bash -s" <<EOF
|
||||||
set -e
|
set -e
|
||||||
SSH_PUBLIC_KEY='$SSH_PUBLIC_KEY'
|
SSH_PUBLIC_KEY='$SSH_PUBLIC_KEY'
|
||||||
SSH_RESTRICTED_KEY_ENTRY='$SSH_RESTRICTED_KEY_ENTRY'
|
SSH_RESTRICTED_KEY_ENTRY='$SSH_RESTRICTED_KEY_ENTRY'
|
||||||
|
|
|
||||||
Loading…
Reference in a new issue