yahoo-eng-team team mailing list archive

[Tom Carroll <Thomas.Carroll@xxxxxxxx>]

Public bug reported:

Version: Liberty
Compute hypervisor: XenServer 6.5SP1
Compute vm: Ubuntu 14.04.3

When a root helper executes commands in another system context,
AsyncProcess.pid returns None. This affects the execution of certain
AsyncProcess's including ovsdb_monitor.

When running with XenServer compute nodes, root_helper = /usr/bin
/neutron-rootwrap-xen-dom0. The wrapper runs in domU while the commands
are executed in dom0. AsyncProcess.pid reteurns None and
AsyncProcess.is_active() returns false. This is due to
utils.get_root_helper_child_pid() return None as the local system cannot
observe the dom0 children processes.

** Affects: neutron
     Importance: Undecided
         Status: New


** Tags: asyncprocess neutron xenserver

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1531273

Title:
  AsyncProcess.pid is None when root helper executes command on another
  system

Status in neutron:
  New

Bug description:
  Version: Liberty
  Compute hypervisor: XenServer 6.5SP1
  Compute vm: Ubuntu 14.04.3

  When a root helper executes commands in another system context,
  AsyncProcess.pid returns None. This affects the execution of certain
  AsyncProcess's including ovsdb_monitor.

  When running with XenServer compute nodes, root_helper = /usr/bin
  /neutron-rootwrap-xen-dom0. The wrapper runs in domU while the
  commands are executed in dom0. AsyncProcess.pid reteurns None and
  AsyncProcess.is_active() returns false. This is due to
  utils.get_root_helper_child_pid() return None as the local system
  cannot observe the dom0 children processes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1531273/+subscriptions