ps to Reproduce
==
It's likely to hit practice if the third-party IVS os-vif plugin
exercises this codepath. Other than that, the way to reproduce this
would be to add back the tests.
** Affects: nova
Importance: Undecided
Assignee: Jan Gutter (jangutter)
Sta
Public bug reported:
* High level description
When sending SIGHUP to the neutron-server process in a neutron_api container,
it looks like the main process locks up in a tight loop. strace output shows
that it's waiting for a process that doesn't exist:
wait4(0, 0x7ffe97e025a4, WNOHANG, NULL) =
a
low-latency virtio port inside the instance, likely backed by hardware
acceleration and requires a supporting Neutron plugin.
* Corresponding neutronclient change:
https://review.openstack.org/#/c/483533/
** Affects: horizon
Importance: Undecided
Assignee: Jan Gutter
Public bug reported:
It might be easier to view the VM plugging process in OpenStack as composed of
three partners, attributes of a Neutron port:
* The VIF edge (plugging in a TAP device into a bridge, configuring a NIC's
VEB, some other form of virtual port manipulation…)
* The VNIC edge (hyper
4 matches
Mail list logo