Question

我正在为Ansible 2.5开发RouterOS网络模块。

RouterOS shell可以打印一些应在on_open_shell()事件中检测到的消息，并自动跳过或关闭。这些是Do you want to see the software license? [Y/n]:和其他一些，所有这些都有详细记录here in the MikroTik Wiki。

以下是我这样做的方式：

def on_open_shell(self):
    try:
        if not prompt.strip().endswith(b'>'):
            self._exec_cli_command(b' ')
    except AnsibleConnectionFailure:
        raise AnsibleConnectionFailure('unable to bypass license prompt')

确实绕过了许可证提示。但是，似乎来自RouterOS设备的\n响应计为后续实际命令的回复。所以，如果我在我的剧本中有两个任务：

---
- hosts: routeros
  gather_facts: no
  connection: network_cli
  tasks:
    - routeros_command:
        commands:
          - /system resource print
          - /system routerboard print
      register: result

    - name: Print result
      debug: var=result.stdout_lines

这是我得到的输出：

ok: [example] => {
    "result.stdout_lines": [
        [
            ""
        ],
        [
            "uptime: 12h33m29s",
            "                  version: 6.42.1 (stable)",
            "               build-time: Apr/23/2018 10:46:55",
            "              free-memory: 231.0MiB",
            "             total-memory: 249.5MiB",
            "                      cpu: Intel(R)",
            "                cpu-count: 1",
            "            cpu-frequency: 2700MHz",
            "                 cpu-load: 2%",
            "           free-hdd-space: 943.8MiB",
            "          total-hdd-space: 984.3MiB",
            "  write-sect-since-reboot: 7048",
            "         write-sect-total: 7048",
            "        architecture-name: x86",
            "               board-name: x86",
            "                 platform: MikroTik"
        ]
    ]
}

正如您所看到的，输出似乎被1抵消了。我该怎么做才能纠正这个问题？

Answer 1

事实证明问题出在定义shell提示符的正则表达式中。我把它定义如下：

terminal_stdout_re = [
    re.compile(br"\[\w+\@[\w\-\.]+\] ?>"),
    # other cases
]

它与提示的结束不匹配，导致Ansible认为在实际命令输出之前有换行符。这是正确的正则表达式：

terminal_stdout_re = [
    re.compile(br"\[\w+\@[\w\-\.]+\] ?> ?$"),
    # other cases
]

Ansible响应中的空字符串

1 个答案: