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
Backport/2.8/55218 #58639
Backport/2.8/55218 #58639
Conversation
(cherry picked from commit 2cdab13)
…andled by edit_macro()
@ajsiersema, just so you are aware we have a dedicated Working Group for network. |
Build succeeded (third-party-check pipeline).
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we have any tests for this?
I'd think there's no need for extra specific tests : "no macro name" is a regular configuration command, it doesn't need any special treatment, i.e. it shouldn't be handled by edit_macro() |
Merged for the 2.8.3 release. |
SUMMARY
Deleting a Cisco IOS macro fails because the "no macro" command was erroneously handled by edit_macro()
Fixes #55212
ISSUE TYPE
COMPONENT NAME
ios_config
ADDITIONAL INFORMATION
STEPS TO REPRODUCE
Try to send a 'no macro name <my_macro_name>' line with ios_config
EXPECTED RESULTS
Macro deleted/undefined on device.
ACTUAL RESULTS
ios_config fails.