yahoo-eng-team team mailing list archive

[Thierry Carrez <thierry.carrez+lp@xxxxxxxxx>]

** Changed in: neutron
       Status: Fix Committed => Fix Released

** Changed in: neutron
    Milestone: None => icehouse-2

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

Title:
  neutron-rootwrap-xen-dom0 does not handle stdin

Status in OpenStack Neutron (virtual network service):
  Fix Released

Bug description:
  To reproduce:

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

  I used Ctrl-D (EOF) on a new line to end input, but it did not
  respond.

  The netwrap process was still running in the dom0 after I Ctrl-C'd.

  ```
  [root@xen ~]# ps aux  | grep netwrap
  root      9987  0.0  0.6   8664  4840 ?        Ss   03:27   0:00 python /etc/xapi.d/plugins/netwrap <methodCall><methodName>run_command</methodName><params><param><value>OpaqueRef:c4567826-fa48-c815-2de8-dbb97bad01cd</value></param><param><value><struct><member><name>cmd</name><value>[&quot;ovs-ofctl&quot;, &quot;add-flows&quot;, &quot;fake-br&quot;, &quot;-&quot;]</value></member></struct></value></param></params></methodCall>
  root     11234  0.0  0.0   4896   716 pts/1    S+   03:29   0:00 grep netwrap
  [root@xen ~]# kill 9987
  ```

  I originally encountered this bug working on blueprint ovs-firewall-
  driver by invoking
  neutron/agent/linux/ovs_lib.py:OvsBridge.defer_apply_off. I have a
  feasible workaround for now by avoiding use of stdin.

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