Prebuilt Ansible Role to manage interface configuration on your Arista EOS Device
BSD 3-Clause "New" or "Revised" License
5
stars
1
forks
source link
module fails if interface doesn't exist and a description is specified #5
Closed
perimore closed 8 years ago
The description commands seem to be pushed before creating an interface:
interfaces:
No loopback on the device at this time, then run the playbook:
TASK [arista.eos-interfaces : Arista EOS interface resources] ** failed: [spine1](item={u'enable': True, u'name': u'Loopback0', u'description': u'Loopback'}) => {"changed": false, "commands": ["configure terminal", "description Loopback", "no shutdown", "interface Loopback0"], "failed": true, "item": {"description": "Loopback", "enable": true, "name": "Loopback0"}, "msg": "matched error in response: description Loopback\r\n% Invalid input\r\nspine-01(config)#"}
The template seems to have an ordering issue.