Description of problem:

When we create fake chassis from functional tests, a new Encap row is created for ip '172.24.4.10' and type 'geneve'. Now, in OVS having duplicated entries in the Encap table is considered a constraint violation and that causes our functional tests to fail.

It doesn't make sense to have two chassis with the same IP address and encap type but for the purpose of functional tests we can just 'fake' it by using different IP addresses. This shouldn't have any side effect as ovn-controller is not running on functional tests and will allow us to still test multiple chassis scenarios.

Version-Release number of selected component (if applicable):


How reproducible:
100%

Steps to Reproduce:
1. Just run: $ tox -edsvm-functional
2.
3.

Actual results:

Some functional tests will fail with:

RuntimeError: OVSDB Error: {"details":"Transaction causes multiple rows in \"Encap\" table to have identical values (geneve and \"192.0.2.2\") for index on columns \"type\" and \"ip\".  First row, with UUID 38d82658-fab2-4257-9706-e17b4e7e0cc9, was inserted by this transaction.  Second row, with UUID efde39d8-0b93-4879-90bb-f1a11c30b9b0, existed in the database before this transaction and was not modified by the transaction.","error":"constraint violation"}


Expected results:

Functional tests to pass

Additional info:

None