As I said earlier in the afternoon, vrouter kernel module is getting loaded in the kernel even before the reboot.
Which causes the vhost0 to be created with the same ip as the original physical interface.(vhost0 and <physicalInt> is holding the same ip).
Which results in two routes to same network one via vhost0 and other via <physicalInt>. So the compute nodes become unreachable.
We will need agent/vrouter teams help in debugging this and identify what causes the kernel module to be loaded.
Pavana/Nipa,
If you have the setup in failed state please share it with agent/vrouter team.
Hi Nipa,
As I said earlier in the afternoon, vrouter kernel module is getting loaded in the kernel even before the reboot.
Which causes the vhost0 to be created with the same ip as the original physical interface.(vhost0 and <physicalInt> is holding the same ip).
Which results in two routes to same network one via vhost0 and other via <physicalInt>. So the compute nodes become unreachable.
We will need agent/vrouter teams help in debugging this and identify what causes the kernel module to be loaded.
Pavana/Nipa,
If you have the setup in failed state please share it with agent/vrouter team.
Thanks,
Ignatious