I have a HWVTEP emulator connected to ODL. When the HWVTEP manager is set to point to the ODL Controller, both controller and HWVTEP see the node as "connected". Configuring L2GW and L2GW connections works, as long as the set-manager config is performed on the HWVTEP AFTER ODL is up and running.

In this same setup, if I unstack/stack (using devstack), and leave the HWVTEP manager config in place, the connection between the HWVTEP and OVSDB on the control node stays connected (via vtep-ctl show, and dumping MDSAL OVSDB connection info for hwvtep dev).

Now, if I configure a L2GW and L2GW connection, the config will not be pushed from the ODL control node to the HWVTEP device. Debugging in the logs shows that L2GW Connection utils doesn't see that the HWVTEP device is connected, even though the HWVTEP DB shows connected, and OVSDB SB MDSAL shows connected.

I don't have the log handy at the moment, will add it to this bug next time I see it.

Suneelu has observed the same behavior. The thinking is that there is possibly some timing issue between OVSDB Connection manager and OVSDB clients.

The workaround for this bug, is to del-manager on HWVTEP device, wait about 30-45 secs, then do a set-manager on HWVTEP device. At this point, L2GW and L2GW Connection config will be sent from ODL to HWVTEP device.