yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #38429
[Bug 1495423] [NEW] Cannot get dom0's ovsdb monitor result
Public bug reported:
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
** Affects: neutron
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
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