Rundeck 未设置环境变量以使用不同的 ssh 端口进行远程执行

Rundeck 将传递给作业的所有选项设置为环境变量，例如$RD_OPTION_*但当作业在具有不同 ssh 端口的远程节点中执行时，它不会设置这些变量。脚本成功登录远程节点，但环境变量不存在。请帮我提供解决方案。

工作定义示例：

<joblist>
  <job>
    <context>
      <options preserveOrder='true'>
        <option name='option1' required='true' />
      </options>
    </context>
    <description>job description</description>
    <dispatch>
      <excludePrecedence>true</excludePrecedence>
      <keepgoing>false</keepgoing>
      <rankOrder>ascending</rankOrder>
      <threadcount>1</threadcount>
    </dispatch>
    <executionEnabled>true</executionEnabled>
    <id>id</id>
    <loglevel>DEBUG</loglevel>
    <name>job name</name>
    <nodefilters>
      <filter>name: remote_node</filter>
    </nodefilters>
    <nodesSelectedByDefault>true</nodesSelectedByDefault>
    <notification>
      <onfailure>
        <email attachLog='true' recipients='[email protected]' subject='job failure :(' />
      </onfailure>
      <onsuccess>
        <email recipients='[email protected]' subject='job succes' />
      </onsuccess>
    </notification>
    <scheduleEnabled>true</scheduleEnabled>
    <sequence keepgoing='false' strategy='step-first'>
      <command>
        <exec>python path/to/script.py $RD_OPTION_OPTION1 > /path/to/logfile_$RD_JOB_EXECID.log 2>&1</exec>
      </command>
      <command>
        <exec>java -jar path/to/jarfile.jar ${option.option1} >> "/path/to/logfile_${job.execid}.log" 2>&1</exec>
      </command>
    </sequence>
    <uuid>job-uuid</uuid>
  </job>
</joblist>

<!-- 
Here
$RD_JOB_EXECID,${job.execid},${option.option1},$RD_OPTION_OPTION1 are not being setup as environment variables when remote node is selected for execution
but the same variables are set up as environment variables when executed locally.
Rundeck logins to the remote node as user successfully.

Log entries are seen in /path/to/logfile_.log file in remote node since $RD_JOB_EXECID has not been set up.

the options @option.option1@ are working fine since they have been replaced by rundeck before executing command.

Rundeck details:
    user: rundeck
    shell: /bin/nologin
    
    rundeck logs into remote server as normal user who has all permissions to execute all these scripts/jars.

-->

Note:

在具有不同 ssh 端口的远程实例上执行时，Rundeck 不会设置环境变量。在本例中，端口为 2808，并且在 resources.xml 中已将其更新为123.456.789.0:2808。 Rundeck 登录服务器并成功执行脚本（没有环境变量）。远程实例 sshd_config 已配置为接受 RD_* 变量。使用端口登录时设置和访问相同的环境变量22.

我认为你搞混了Rundeck 命令参数 and Rundeck环境变量

这是“命令、脚本参数和作业参考参数”：${job.execid}

正如其名称所示，您可以将其用作命令参数。就像您在工作定义中所做的那样。

这是一个“环境变量”：$RD_JOB_EXECID

无需任何设置，如果您在 Rundeck 服务器本身上运行作业，则两者都可以正常工作，但如果您想将作业分派到节点，$RD_JOB_EXECID无法开箱即用。

要通过远程命令调度传递环境变量，它是 需要在远程端正确配置 SSH 服务器。看 “sshd_config(5)”中的 AcceptEnv 指令手册页为了 指示。

使用通配符模式允许 RD_ 前缀变量提供 开放对 Rundeck 生成的环境变量的访问。

 Example in sshd_config:

 # pass Rundeck variables 
 AcceptEnv RD_*

Rundeck SSH 插件

在 Rundeck 服务器上

确保你有SendEnv RD_*在 ssh_config 中设置

对于您的用例，${job.execid},${option.option1}可以完美地工作，不会弄乱 sshd_config

它确实可以在不同的 SSH 端口上工作。

XML 中的职位定义

<joblist>
  <job>
    <context>
      <options preserveOrder='true'>
        <option name='nodeFilter' />
      </options>
    </context>
    <description></description>
    <dispatch>
      <excludePrecedence>true</excludePrecedence>
      <keepgoing>false</keepgoing>
      <rankOrder>ascending</rankOrder>
      <threadcount>1</threadcount>
    </dispatch>
    <executionEnabled>true</executionEnabled>
    <group>TEST</group>
    <id>63b6f283-39b2-479d-bba9-b1742bc2ea53</id>
    <loglevel>INFO</loglevel>
    <name>test rundeck job context</name>
    <nodefilters>
      <filter>${option.nodeFilter}</filter>
    </nodefilters>
    <nodesSelectedByDefault>true</nodesSelectedByDefault>
    <scheduleEnabled>true</scheduleEnabled>
    <sequence keepgoing='false' strategy='node-first'>
      <command>
        <script><![CDATA[#!/usr/bin/python
import sys
print "I know ENV_VAR will not work as command line arguments %s " % sys.argv
]]></script>
        <scriptargs> "&gt;${job.execid}&lt; &gt;$RD_JOB_EXECID&lt;"</scriptargs>
      </command>
      <command>
        <script><![CDATA[#!/bin/bash
echo "But it works in Bash"
echo $RD_JOB_ID
echo $RD_JOB_EXECID

echo "Which port does sshd listening on?"
sudo netstat -tulpn | grep 2808]]></script>
        <scriptargs />
      </command>
    </sequence>
    <uuid>63b6f283-39b2-479d-bba9-b1742bc2ea53</uuid>
  </job>
</joblist>