FWIW, I don't believe that the commit referenced in comment #9 is related to the problem, unless there's a race condition introduced by the added delay. Looking at that commit, the code will try harder to make sure that the device in the namespace exists before proceeding on as it did before. The log shows the error messages because the referenced change introduced a log message for the condition that the device doesn't exist in the namespace. The code in that code path continues as it did previously even when the error is logged. As a result, that change primarily waits up to 3 seconds longer for the device to exist and will then log the error for awareness, but still continues in the same code path.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927868 Title: vRouter not working after update to 16.3.1 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1927868/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
