-
Notifications
You must be signed in to change notification settings - Fork 659
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
Subinterface vrf bind issue fix #2211
Conversation
This pull request introduces 1 alert and fixes 1 when merging 380339c into a3d1345 - view on LGTM.com new alerts:
fixed alerts:
|
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.
Please add UT to cover both the fixes
config/main.py
Outdated
if interface_type == "VLAN_SUB_INTERFACE": | ||
subintf = config_db.get_entry(interface_type, alias) | ||
if 'vrf_name' in subintf_entry: | ||
subintf_entry.pop('vrf') |
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.
Can you explain the logic here? Why should vrf be popped?
Can you please add Unit tests? |
@preetham-singh @adyeung Can you please share ETA to add the unit tests? |
Sure, I will update tunit tests by 7/15. |
format Update "show subniterface status" to reflect subinterface in user configured long name and short name format.
1. Short Format Subinterface getting deleted after vrf binding . Issue 10802:sonic-net/sonic-buildimage#10802 2. Do not allow short format subinterface to be created without encap vlan configuration. Issue 10878: sonic-net/sonic-buildimage#10878
1. Short Format Subinterface getting deleted after vrf binding . Issue 10802:sonic-net/sonic-buildimage#10802 2. Do not allow short format subinterface to be created without encap vlan configuration. Issue 10878: sonic-net/sonic-buildimage#10878
instead update existing subinterface. Updating unit testcases for subinterfaces.
@preetham-singh Can you please check the coverage failure? |
Hi @adyeung @preetham-singh Can you please solve the build failure? |
Adam will follow up. Thanks |
Working with SONiC team to resolve code coverage issue for VRF BIND CLI. I will update the PR once code coverage scripts are updated for VRF Bind CLI. |
This test failure should get resolved once PR #2309 is merged. |
/azpw run Azure.sonic-utilities |
/AzurePipelines run Azure.sonic-utilities |
Azure Pipelines successfully started running 1 pipeline(s). |
* Add support to configure routed subinterface in short name and long name format * Update "show subniterface status" to reflect subinterface in user configured long name and short name format.
Update sonic-utilities submodule pointer to include the following: * [route_check]: Ignore standalone tunnel routes (sonic-net#2325) ([sonic-net#2346](sonic-net/sonic-utilities#2346)) * [VRF]Adding CLI checks to ensure Vrf is valid in interface bind and static route commands ([sonic-net#2333](sonic-net/sonic-utilities#2333)) * Subinterface vrf bind issue fix ([sonic-net#2211](sonic-net/sonic-utilities#2211)) * [decode-syseeprom] Fix setting use_db based on support_eeprom_db ([sonic-net#2270](sonic-net/sonic-utilities#2270)) * Fix vrf UT failed issue ([sonic-net#2309](sonic-net/sonic-utilities#2309)) Signed-off-by: dprital <drorp@nvidia.com>
Update sonic-utilities submodule pointer to include the following: * [route_check]: Ignore standalone tunnel routes (#2325) ([#2346](sonic-net/sonic-utilities#2346)) * [VRF]Adding CLI checks to ensure Vrf is valid in interface bind and static route commands ([#2333](sonic-net/sonic-utilities#2333)) * Subinterface vrf bind issue fix ([#2211](sonic-net/sonic-utilities#2211)) * [decode-syseeprom] Fix setting use_db based on support_eeprom_db ([#2270](sonic-net/sonic-utilities#2270)) * Fix vrf UT failed issue ([#2309](sonic-net/sonic-utilities#2309)) Signed-off-by: dprital <drorp@nvidia.com> Signed-off-by: dprital <drorp@nvidia.com>
What I did
This commit addresses below issues:
How I did it
How to verify it
Previous command output (if the output of a command-line utility has changed)
New command output (if the output of a command-line utility has changed)