Closed emptythevoid closed 2 years ago
Sorry. This was a weird side-effect of a "commit" being sent when each task was complete. I had a lengthy VPN setup I was trying to automate. ALL of the required set commands must be in the same task so that everything gets committed at the same time.
Attempting to run a set command using community.network.edgeos_config that includes an IP address results in a failure.
Expected:
lines:
- set interfaces ethernet eth4 address 10.0.1.1/24
should result in a changed or OK status
Result: The set command fails with the error below (this seems to happen any set command I've tried that includes an IP address)
The full traceback is: WARNING: The below traceback may not be related to the actual failure. File "/tmp/ansible_community.network.edgeos_config_payload_KZLsG0/ansible_community.network.edgeos_config_payload.zip/ansible_collections/community/network/plugins/module_utils/network/edgeos/edgeos.py", line 124, in load_config out = connection.commit(comment) File "/tmp/ansible_community.network.edgeos_config_payload_KZLsG0/ansible_community.network.edgeos_config_payload.zip/ansible/module_utils/connection.py", line 185, in rpc raise ConnectionError(to_text(msg, errors='surrogate_then_replace'), code=code) fatal: [edgerouter30]: FAILED! => { "changed": false, "invocation": { "module_args": { "backup": false, "backup_options": null, "comment": "configured by edgeos_config", "config": null, "lines": [ "set interfaces ethernet eth4 address 10.0.1.1/24" ], "match": "line", "save": false, "src": null } }, "msg": "commit failed: None" }
I tested the same commands into an SSH session with the edgerouter and it was accepted properly.
Ansible 2.9.6 EdgeRouter firmware: 1.10.7