Wrong mac affected to the external-ids:attached-mac

[Christophe Sauthier]

Using today devstack

At the creation of a container, the mac affected to the external-ids:attached-mac of the br-int-side-device (seen in ovs-vsctl --columns=name,external-ids list Interface) is different from the one that is affected by the associated neutron-port.
The result is that the communication between 2 containers is possible, but no communication is possible with the various instances that are runned by OpenStack (or the attached router)

Fixing that mac address (with the command ovs-vsctl set interface br-int-side-device external-ids:attached-mac=$correct_mac) to the same of enables that commuication.

[Mohammad Banikazemi (mb-s)]

@Christophe \Can you please explain what you mean by "no communication is possible with the various instances that are runned by OpenStack (or the attached router)". By "various instances" are you referring to VMs connected to the same network? Please elaborate. I would like to reproduce the problem.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/305790

[Christophe Sauthier (christophe.sauthier)]

I have used the default devstack configuration file that is given in the kuryr git repository
https://github.com/openstack/kuryr/blob/master/devstack/local.conf.sample

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/305790
Committed: https://git.openstack.org/cgit/openstack/kuryr/commit/?id=eefe1dbd64b79d1d764ffdc42166d52139b5965a
Submitter: Jenkins
Branch: master

commit eefe1dbd64b79d1d764ffdc42166d52139b5965a
Author: Christophe Sauthier <email address hidden>
Date: Thu Apr 14 13:59:56 2016 +0200

    Fix ovs creation of the port

    This patch fix the mac address of the port to the right value.
    It also creates the port atomically (with the various details),
    avoiding it to be misinterpreted by ovs-agent.

    Change-Id: I16f89a30ac3b47eeaa5edddd37712934729fdf93
    Closes-Bug: 1569412