yahoo-eng-team team mailing list archive

[Alin Balutoiu <abalutoiu@xxxxxxxxxxxxxxxxxxxxxx>]

Public bug reported:

The neutron OVS agent on Windows does not set the tags on the VM ports
when using the native implementation.

There is no error shown in the logs, the the port does not have any tags.
>From the following output of the command "ovs-vsctl show" (http://paste.openstack.org/show/601605/) we can see that the VM port named "65b8a556-6d1a-4f9f-aa38-347b0edfa494" under br-int does not have any tags associated with it.

If the agent is restarted on the host, it will fail to start again with
the following trace: http://paste.openstack.org/show/601606/

Expected behaviour: The VM port present under bridge br-int should have
an associated tag set.

** Affects: neutron
     Importance: Undecided
     Assignee: Alin Balutoiu (abalutoiu)
         Status: In Progress

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

Title:
  Neutron OVS Agent does not set the tag for the ports

Status in neutron:
  In Progress

Bug description:
  The neutron OVS agent on Windows does not set the tags on the VM ports
  when using the native implementation.

  There is no error shown in the logs, the the port does not have any tags.
  From the following output of the command "ovs-vsctl show" (http://paste.openstack.org/show/601605/) we can see that the VM port named "65b8a556-6d1a-4f9f-aa38-347b0edfa494" under br-int does not have any tags associated with it.

  If the agent is restarted on the host, it will fail to start again
  with the following trace: http://paste.openstack.org/show/601606/

  Expected behaviour: The VM port present under bridge br-int should
  have an associated tag set.

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