Comment 34 for bug 1715374

Revision history for this message
Matt Riedemann (mriedem) wrote :

I created a train devstack today:

commit 683454f319246c3bda088b5e0325c5673263ce08 (HEAD -> master, origin/master, origin/HEAD)
Merge: 13e260ea 7224a6b5
Author: Zuul <email address hidden>
Date: Wed Apr 3 06:39:52 2019 +0000

    Merge "Update docs index page"

And created a test VM, it was fine. Then I SIGHUP'ed <email address hidden>:

sudo systemctl kill -s HUP <email address hidden>

I watched the n-cpu logs to make sure it was doing the reset() logic as expected, which it did. Then I tried creating another server which failed in privsep calls in the libvirt driver:

http://paste.openstack.org/show/748820/

Then when trying to cleanup and unplug VIFs privsep failed again:

http://paste.openstack.org/show/748821/

I couldn't get past this until I restarted <email address hidden>.

So unless there is some weird configuration with privsep + nova-compute in devstack, we have bigger issues than just temporarily not getting network-vif-plugged callbacks registered, but I don't know if the privsep stuff is a recent regression or not in this flow.