Executing Ansible Node in Runbook

Once the definition is completed, click Run to execute the Ansible node and view its execution log. The following is a sample of execution log:

Note: In order to successfully execute the Ansible playbook, following conditions must be met prior to clicking the Run button:

- You need to sign in with Change Management License to view/edit/execute the Ansible node.

- You need to request approval of the Change Management Runbook.

- The playbook cannot be blank.

Tip: Due to some known issues of the latest versions of RedHat Ansible, if you notice any unfamiliar errors in execution log when running Anisble task, you can perform quick troubleshooting yourself by logging in to the Ansible server and running the playbooks manually.


Ansible supports the Dry-run mode to simulate Ansible node execution process. To perform Dry-run, you must sign in with Network Change Creator permission or Network Change Executor permission. Clicking Dry-run hyperlink will generate Dry-run Log containing Dry-run results.

Terminate button can be used to force stop the Ansible task running on the Linux server. However, it is not recommended to perform force stop unless it’s necessary (such as un-responding process), as it may cause unknown system failure.

Note: Dry-run on multiple Ansible agents is not supported.

Execution Options

NetBrain inherits many command line options supported by Ansible to execute the playbook. See Ansible Command Line Parameters for more information.

Execution Option dialogue can be launched by clicking the setting icon on the bottom-right corner of the dialogue.