Skip to content

Voq chassis end to end Ping tests fail #9021

@judyjoseph

Description

@judyjoseph

Description

Few of the voq end to end tests fail. The tests are : voq/test_voq_ipfwd.py::TestVoqIPFwd::test_voq_end_to_end_ping, voq/test_voq_ipfwd.py::test_ipforwarding_jumbo_to_dut and few of test_voq_disrupts testcases.

The loopback route advt are getting filtered ( by RH route-maps) on the T2 chassis based on the BGP neighborship type as RegionalHub/AZNGHub -- If the DEVICE_NEIGHBOR_METADATA type is RegionalHub the loopback ip is filtered

This results in ping failure from T1 --> T3 as the reachability to loopback is not present in routing table for those "type" BGP neighbors. Mostly we should be able to fix this in tests - checking on that.

Steps to reproduce the issue:

  1. Run voq/test_voq_ipfwd.py::TestVoqIPFwd::test_voq_end_to_end_ping, voq/test_voq_ipfwd.py::test_ipforwarding_jumbo_to_dut

Describe the results you received:
End to End ping failure

Describe the results you expected:
ping should pass

Additional information you deem important:

**Output of `show version`:**

```

admin@svcstr-7250-lc1-1:~$ show version

SONiC Software Version: SONiC.20220530.36
SONiC OS Version: 11
Distribution: Debian 11.7
Kernel: 5.10.0-18-2-amd64
Build commit: dfd7ce3082
Build date: Fri Jul 14 04:56:49 UTC 20
```

**Attach debug file `sudo generate_dump`:**

```
(paste your output here)
```

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions