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
I expect this playbook to succeed when the state of the devices is already disconnected, but instead it fails saying that the connection is not active.
Actual Results
$ ansible-playbook -i inventory.yaml set_up_network_interfaces.yaml...TASK [Disable all enp* connections] ******************************************************************************************************skipping: [metal] => (item=lo)failed: [metal] (item=enp129s0f0np0) => {"ansible_loop_var": "item", "changed": false, "item": "enp129s0f0np0", "msg": "Error: 'enp129s0f0np0' is not an active connection.\nError: no active connection provided.\n", "name": "No Connection named enp129s0f0np0 exists", "rc": 10}failed: [metal] (item=enp129s0f1np1) => {"ansible_loop_var": "item", "changed": false, "item": "enp129s0f1np1", "msg": "Error: 'enp129s0f1np1' is not an active connection.\nError: no active connection provided.\n", "name": "No Connection named enp129s0f1np1 exists", "rc": 10}skipping: [metal] => (item=eno1)
Code of Conduct
I agree to follow the Ansible Code of Conduct
The text was updated successfully, but these errors were encountered:
Summary
When setting a connection's state to "down" using the
nmcli
module, the task fails if the connection is already down.Issue Type
Bug Report
Component Name
nmcli
Ansible Version
Community.general Version
Configuration
No response
OS / Environment
The target system is running
RHEL 9.4
, the host system is runningUbuntu 22.04.5
.Steps to Reproduce
Expected Results
I expect this playbook to succeed when the state of the devices is already disconnected, but instead it fails saying that the connection is not active.
Actual Results
Code of Conduct
The text was updated successfully, but these errors were encountered: