-
Notifications
You must be signed in to change notification settings - Fork 23.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
eos_eapi doesn't enable non-default vrfs if the default vrf is already configured #32111
Labels
affects_2.4
This issue/PR affects Ansible v2.4
bug
This issue/PR relates to a bug.
module
This issue/PR relates to a module.
networking
Network category
support:network
This issue/PR relates to code supported by the Ansible Network Team.
Milestone
Comments
ansibot
added
affects_2.4
This issue/PR affects Ansible v2.4
bug_report
module
This issue/PR relates to a module.
needs_triage
Needs a first human triage before being processed.
networking
Network category
support:network
This issue/PR relates to code supported by the Ansible Network Team.
labels
Oct 25, 2017
looks like the check on whether the no shutdown command is entered needs to see if the current vrf is the one that the user is trying to enable as well |
resolved_by_pr: 32112 |
gundalow
removed
the
needs_triage
Needs a first human triage before being processed.
label
Oct 25, 2017
caphrim007
pushed a commit
to caphrim007/ansible
that referenced
this issue
Nov 1, 2017
…e#32111 (ansible#32112) * adding the desired state config to the new vrf fixes ansible#32111 * fix default vrf initial configured * add unit test
ganeshrn
pushed a commit
to ganeshrn/ansible
that referenced
this issue
Nov 1, 2017
…e#32111 (ansible#32112) * adding the desired state config to the new vrf fixes ansible#32111 * fix default vrf initial configured * add unit test * Update CHANGELOG (cherry picked from commit 2c99cbc)
ganeshrn
pushed a commit
to ganeshrn/ansible
that referenced
this issue
Nov 1, 2017
…e#32111 (ansible#32112) * adding the desired state config to the new vrf fixes ansible#32111 * fix default vrf initial configured * add unit test * Update CHANGELOG (cherry picked from commit 2c99cbc)
Fix will be available in 2.4.2beta2 release |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
affects_2.4
This issue/PR affects Ansible v2.4
bug
This issue/PR relates to a bug.
module
This issue/PR relates to a module.
networking
Network category
support:network
This issue/PR relates to code supported by the Ansible Network Team.
ISSUE TYPE
COMPONENT NAME
eos_eapi
ANSIBLE VERSION
CONFIGURATION
n/A
OS / ENVIRONMENT
N/A
SUMMARY
When a eos device has the eapi feature configured in the default vrf (i.e the running config has this):
When you run the following task:
The non-default vrf doesn't get the 'no shutdown' command
so you end up with a state like this:
On the switch there is only the default one remains, since the command sent via ansible does not no shut the non-default vrf.
STEPS TO REPRODUCE
EXPECTED RESULTS
The play should send a no shutdown command for the non-default vrf
ACTUAL RESULTS
The text was updated successfully, but these errors were encountered: