Description
VNET test generates more VNET route endpoints than specified by the --num_endpoints argument.
Steps to reproduce the issue:
- Run VNET test with the following arguments:
--num_vnet=32 --num_routes=40000 --num_endpoints=4000:
py.test vxlan/test_vnet_vxlan.py --inventory "../ansible/inventory, ../ansible/veos" --host-pattern <testbed-name> --module-path ../ansible/library/ --testbed <testbed-name> --testbed_file ../ansible/testbed.csv -v --num_vnet=32 --num_routes=40000 --num_endpoints=4000
- Go to the switch console and check genertated config.
- Observe that test generated configs with more routes and endpoints that were passed by arguments:
root@sonic:/home/admin# grep endpoint /tmp/vnet.route.json | sort -u | wc -l
4016
root@sonic:/home/admin# grep VNET_ROUTE /tmp/vnet.route.json | wc -l
40084
root@sonic:/home/admin#
Describe the results you received:
Test generated configs with more routes and endpoints that were passed by arguments:
root@sonic:/home/admin# grep endpoint /tmp/vnet.route.json | sort -u | wc -l
4016
root@sonic:/home/admin# grep VNET_ROUTE /tmp/vnet.route.json | wc -l
40084
root@sonic:/home/admin#
Describe the results you expected:
Test should generate same number of VNET routes and endpoints as was passed by arguments.
Additional information you deem important:
**Output of `show version`:**
```
(paste your output here)
```
**Attach debug file `sudo generate_dump`:**
```
(paste your output here)
```
Description
VNET test generates more VNET route endpoints than specified by the
--num_endpointsargument.Steps to reproduce the issue:
--num_vnet=32 --num_routes=40000 --num_endpoints=4000:Describe the results you received:
Test generated configs with more routes and endpoints that were passed by arguments:
Describe the results you expected:
Test should generate same number of VNET routes and endpoints as was passed by arguments.
Additional information you deem important: