Reverted VNET Vxlan test params to prevent route configuration issues#8379
Reverted VNET Vxlan test params to prevent route configuration issues#8379bingwang-ms merged 1 commit intosonic-net:masterfrom
Conversation
|
The pre-commit check detected issues in the files touched by this pull request. Detailed pre-commit check results: To run the pre-commit checks locally, you can follow below steps:
|
…onic-net#8379) (sonic-net#11530) - Why I did it New SN410 A1 system has a different sensor layout with A0 system, needs a new sensor conf file to support it. - How I did it Since the SN4410 A1 system use exactly the same sensor layout as the SN4700 A1 system, so add a symbol link linking to the SN4700 A1 sensor conf file to reuse. - How to verify it Run sensor test against the SN4410 A1 system; Run platform related regression test against the SN4410 A1 system
Description of PR
Vnet Vxlan test fails with the current params: 16K routes, 1 vnets, and 4K endpoints.
The test fails due to a combination of ipv4 and ipv6 tunnels, due to ipv6 parameter enabled on sonic-mgmt branch.
The ipv6 is disabled on 202205 branch, and the number of vnets is 1 instead of 8 in the 202211 branch.
The PR reverts the parameters back to the 202205 values, the test passes with those parameters.
Summary:
The PR is related to bug #8374, where the route configuration is not applied correctly.
The PR is reverting the test params back to 202205 configuration.
Type of change
Back port request
Approach
What is the motivation for this PR?
Reverting changes done on #6212, which changes the parameters of the test, as the test doesn't pass with them.
How did you do it?
Changed the parameter on conftest.py to 202205 conf
How did you verify/test it?
ran the vnet_vxlan test parameters with 202205 a few times.
Any platform specific information?
Runs on to topo.