[IOS-XR] Fix show l2vpn bridge-domain detail : Parses variations in the EVI field format correctly#907
Conversation
1fae532 to
afd0682
Compare
This comment was marked as resolved.
This comment was marked as resolved.
afd0682 to
9aa193c
Compare
|
Hi there! 👋 Best regards, |
3c4e60a to
07af294
Compare
|
Hi team, This PR was opened on Oct 29, 2024, and it's been over a year now. The build is failing in Python 3.9 job due to "Error: Version 3.9 with arch x64 not found" in actions/setup-python@v1 (available: 3.10+), which this PR doesn't affect. Could you please review and merge it when possible? I'd love to install the official version soon. Thanks! |
2ee3c26 to
8670db6
Compare
…ail parser - Modified `p63` regex in `show_l2vpn.py` to support optional suffix (e.g., "(SRv6)") for EVI values - Updated `golden9_expected.py` to reflect new test output for EVI field - Adjusted URL in `github_parser.json` for the updated line reference These changes enhance the parser's compatibility with new formats in `ShowL2vpnBridgeDomainDetail`.
8670db6 to
ae0e069
Compare
Verified: current
|
| Test | This branch | genie/main (old parser) |
|---|---|---|
| golden1–8 | PASS | PASS |
golden9 (with evi: 1002 (SRv6)) |
PASS | FAIL |
| empty | PASS | PASS |
Branch has been rebased on genie/main (285024fb0) and force-pushed.
PR checklist status
- Changelog:
changelog/undistributed/changelog_show_l2vpn_bridge_domain_detail_iosxr_20241029105539.rst make json: updated (1 line number shift ingithub_parser.json)- All 10 tests pass on this branch
- No regressions on existing tests
p63regex inshow_l2vpn.pyto support optional suffix (e.g., "(SRv6)") for EVI valuesgolden9_expected.pyto reflect new test output for EVI fieldgithub_parser.jsonfor the updated line referenceThese changes enhance the parser's compatibility with new formats in
ShowL2vpnBridgeDomainDetail.Description
The
ShowL2vpnBridgeDomainDetailparser for IOS-XR devices was not handling some variations in the EVI field format correctly, resulting in parsing errors or missed data. Specifically, when the evi field includes additional suffix information (e.g., (SRv6)), the parser could not match this pattern and failed to extract the EVI value.Motivation and Context
Closes #906
Checklist: