SYMC:Same IP is being assigned to ports and service instances

[Rudrajit Tapadar]

After the upgrade to 2.02 build 59 we got user complaints that they are being kicked out of ssh sessions frequently. On investigating, I found that LBaaS and VM ports have same IPs assigned and hence flows are only intermittently set up on a hypervisor.

[Prakash Bailkeri (prakashmb)]

Looks like duplicate ip address allocation issue. Can you check the zookeeper status and validity of data after upgrade? How the zookeeper data backed/restored in the upgrade process?

Also, please confirm which object existed before upgrade and which one is created after upgrade? Whether the VM was created before upgrade or LBaas? I assume by LBaas you are referring to VIP address allocated for LBaas.

Can you please get the api server logs(contrail-api-0-stdout.log* and contrail-api.log.* along with api-0-zk.log* to check the address allocation issue?

[Rudrajit Tapadar (rtapadar)]

Zookeeper is running on the db nodes. The db nodes were not touched in this upgrade and they are still running 2.01-43, only controllers and vrouters were upgraded to 2.02-59.

Objects created before and after the upgrade both are affected by IP conflicts. I have provided all the logs in the slack channel.