BGP internal/external distance deviation
Deviation for RT-1.34.
Deviation configured internal/external BGP distance using CLI call as OC is unsupported
Pull Request Functional Test Report for #3564 / 42e497f666fbe5fe30d3ea7f649906ef6055b651
Virtual Devices
| Device | Test | Test Documentation | Job | Raw Log |
|---|---|---|---|---|
| Arista cEOS | RT-1.34: BGP route-distance configuration |
|||
| Cisco 8000E | RT-1.34: BGP route-distance configuration |
|||
| Cisco XRd | RT-1.34: BGP route-distance configuration |
|||
| Juniper ncPTX | RT-1.34: BGP route-distance configuration |
|||
| Nokia SR Linux | RT-1.34: BGP route-distance configuration |
|||
| Openconfig Lemming | RT-1.34: BGP route-distance configuration |
Hardware Devices
| Device | Test | Test Documentation | Raw Log |
|---|---|---|---|
| Arista 7808 | RT-1.34: BGP route-distance configuration |
||
| Cisco 8808 | RT-1.34: BGP route-distance configuration |
||
| Juniper PTX10008 | RT-1.34: BGP route-distance configuration |
||
| Nokia 7250 IXR-10e | RT-1.34: BGP route-distance configuration |
Pull Request Test Coverage Report for Build 14897222674
Details
- 7 of 24 (29.17%) changed or added relevant lines in 2 files are covered.
- 3 unchanged lines in 1 file lost coverage.
- Overall coverage increased (+0.03%) to 18.057%
| Changes Missing Coverage | Covered Lines | Changed/Added Lines | % |
|---|---|---|---|
| internal/deviations/deviations.go | 0 | 3 | 0.0% |
| proto/metadata_go_proto/metadata.pb.go | 7 | 21 | 33.33% |
| <!-- | Total: | 7 | 24 |
| Files with Coverage Reduction | New Missed Lines | % |
|---|---|---|
| proto/metadata_go_proto/metadata.pb.go | 3 | 5.42% |
| <!-- | Total: | 3 |
| Totals | |
|---|---|
| Change from base Build 14886848089: | 0.03% |
| Covered Lines: | 2479 |
| Relevant Lines: | 13729 |
💛 - Coveralls
/fptest virtual
/fptest virtual
/fptest cisco-8808
Hi @manan-patel there are still conflicts
/fptest virtual
@manan-patel @arvbaska1 Problem is that this deviations is using a CLI and it is not acceptable now. Is there another way to fix this? Can we explore a native OC path support for this one until we get support on this feature?
@manan-patel @arvbaska1 Problem is that this deviations is using a CLI and it is not acceptable now. Is there another way to fix this? Can we explore a native OC path support for this one until we get support on this feature?
Hello @manan-patel @arvbaska1 - Based on the discussion internally, now we are accepting the CLI as an alternate via deviation. But make sure we have a tracking bug raised for the deviation.
@manan-patel @arvbaska1 - Can you please resolve the conflicts, so i can validate the PR and close on it.