Comment 2 for bug 1495423

Revision history for this message
huan (huan-xie) wrote : RE: [Bug 1495423] Re: Cannot get dom0's ovsdb monitor result

Hi,
This is a different bug from that one I reported.
But I think the two bugs have some connection with each other.
I mean, once this bug is fixed, maybe we can also fix that one.

BR//Huan

-----Original Message-----
From: <email address hidden> [mailto:<email address hidden>] On Behalf Of Rossella Sblendido
Sent: Monday, September 14, 2015 5:26 PM
To: Huan Xie
Subject: [Bug 1495423] Re: Cannot get dom0's ovsdb monitor result

huan is this different from the other bug you filed [1] ?

[1] https://bugs.launchpad.net/neutron/+bug/1493662

--
You received this bug notification because you are subscribed to the bug report.
https://bugs.launchpad.net/bugs/1495423

Title:
  Cannot get dom0's ovsdb monitor result

Status in neutron:
  New

Bug description:
  With Xenserver+Neutron, ML2 plugin, OVS driver, VLAN typs

  When launching a new instance, the q-agt which runs in compute node cannot get the new instance's port changes in dom0's ovsdb.
  This makes the q-agt cannot add the coresponding tag for this port and lead the instance cannot get IP from dhcp.
  Because without correct tag, OVS flow rules will drop all the package from this instance to DHCP agent.

  The dom0's ovsdb monitor output is got via netwrap which resides in
  dom0

  neutron\neutron\plugins\ml2\drivers\openvswitch\agent\xenapi\etc\xapi.d\plugins\netwrap

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