OOO:DPDK Agent restart alone doesnot bringup vhost0

[Vinod Nair]

On A tripleo Provisioned dpdk cluster, on restarting agent , vhost0 doesnot come up

ip link | grep vhost
20: vhost0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT qlen 1000

[root@dpdk-contraildpdk-1 heat-admin]# contrail-status
== Contrail vRouter ==
supervisor-vrouter: active
contrail-vrouter-agent timeout
contrail-vrouter-dpdk active
contrail-vrouter-nodemgr initializing

Workaround: Restart supervisor-vrouter

[Kiran (kiran-kn80)]

other workaround: once the agent status goes to "timeout" state, do the following:

ifup vhost0
ifconfig vhost0 hw ether <mac address of vhost0>

[Ankit Chadha (achadha)]

There are 2 aspects to this bug:

1. On agent side: Handling ifup within agent code (when agent is restarted)
2. On provisioning side: writing vhost0's MAC address to ifcfg-vhost0 at the time of provisioning.

[Jeba Paulaiyan (jebap)]

Release-Notes:
==============
On a RHOSP10 provisioned cluster, if the grouter-agent gets restarted, vhost0 interface does not come up. "service supervisor-vrouter restart" will bring the service back up.

[Ankit Chadha (achadha)]

Here's the plan for this feature:

3.2: Release noted
4.x: This bug would be resolved once the ifup scripts are ready for kernel/dpdk modes. The idea is not to use vrouter-functions.sh at all (in a Director based installation).