b440544e73
Fixes #36979 If `abort` is not issued in the top level session prompt the existing session goes to pending state. The fix is to come out of config mode by issuing `end` command and again to same config session and execute `abort` which `abort` is issued at the top level session prompt.
40 lines
944 B
YAML
40 lines
944 B
YAML
---
|
|
- debug: msg="START cli/check_mode.yaml on connection={{ ansible_connection }}"
|
|
|
|
- name: invalid configuration in check mode
|
|
eos_config:
|
|
lines:
|
|
- ip address 119.31.1.1 255.255.255.256
|
|
parents: interface Loopback911
|
|
check_mode: 1
|
|
environment:
|
|
ANSIBLE_EOS_USE_SESSIONS: 1
|
|
register: result
|
|
ignore_errors: yes
|
|
|
|
- assert:
|
|
that:
|
|
- "result.msg is defined"
|
|
- "result.failed == true"
|
|
- "'Error on executing commands' in result.msg"
|
|
|
|
- name: valid configuration in check mode
|
|
eos_config:
|
|
before:
|
|
- "no ip access-list test"
|
|
src: basic/cmds.j2
|
|
check_mode: yes
|
|
register: config
|
|
|
|
- name: check if session is removed
|
|
eos_command:
|
|
commands:
|
|
- show configuration sessions | json
|
|
provider: "{{ cli }}"
|
|
register: result
|
|
|
|
- assert:
|
|
that:
|
|
- "config.session not in result.stdout[0].sessions"
|
|
|
|
- debug: msg="END cli/check_mode.yaml on connection={{ ansible_connection }}"
|