The workaround for this is to re-enable DHCP on the affected subnet. However, this triggers another bug, wherein the route for default gateway x.y.z.1/32 disappears on all hypervisors that have VMs in the affected subnet. Restarting contrail-vrouter-agent on affected hypervisors re-downloads the route and things get back to normal.
The workaround for this is to re-enable DHCP on the affected subnet. However, this triggers another bug, wherein the route for default gateway x.y.z.1/32 disappears on all hypervisors that have VMs in the affected subnet. Restarting contrail- vrouter- agent on affected hypervisors re-downloads the route and things get back to normal.