neutron linux bridge agent is buggy and can not boot instance

[Jeffrey Zhang]

when booting vm in a neutron linux bridge env, the vm will be failed.

[Ganesh Maharaj Mahalingam (ganesh-mahalingam)]

Should tie https://bugs.launchpad.net/kolla/+bug/1566543 to this one.

[Vikram Hosakote (vhosakot)]

https://review.openstack.org/#/c/302721/ is proposed to fix this.

[Carlos Cesario (ccesario)]

Hi guys, this patch set https://review.openstack.org/#/c/302721/14 it seems fix the problem.

In my tests the deploy it works. More details in http://paste.openstack.org/show/493863/

[Carlos Cesario (ccesario)]

Hello, only to update:

I know that is can be other problem but I would like to register in this bug page:

root@kolla-network:~# docker exec -it neutron_linuxbridge_agent bash
(neutron-linuxbridge-agent)[neutron@kolla-network /]$ ip netns list
qrouter-d9794753-c16f-45fe-923a-df8797641121
qdhcp-e20db26a-f25d-4b9b-ae58-ebb156006aa7
(neutron-linuxbridge-agent)[neutron@kolla-network /]$ ip netns exec qrouter-d9794753-c16f-45fe-923a-df8797641121 ifconfig
Cannot open network namespace "qrouter-d9794753-c16f-45fe-923a-df8797641121": Permission denied
(neutron-linuxbridge-agent)[neutron@kolla-network /]$ ip netns exec qdhcp-e20db26a-f25d-4b9b-ae58-ebb156006aa7 ifconfig
Cannot open network namespace "qdhcp-e20db26a-f25d-4b9b-ae58-ebb156006aa7": Permission denied
(neutron-linuxbridge-agent)[neutron@kolla-network /]$ ip netns exec qdhcp-e20db26a-f25d-4b9b-ae58-ebb156006aa7 ip a
Cannot open network namespace "qdhcp-e20db26a-f25d-4b9b-ae58-ebb156006aa7": Permission denied
(neutron-linuxbridge-agent)[neutron@kolla-network /]$ sudo ip netns exec qrouter-d9794753-c16f-45fe-923a-df8797641121 ifconfig
[sudo] password for neutron:
Sorry, try again.
[sudo] password for neutron:
Sorry, try again.
[sudo] password for neutron:
sudo: 2 incorrect password attempts
(neutron-linuxbridge-agent)[neutron@kolla-network /]$

In this case what is the correct way to exec commands in netns objects ?
Can this to be a problem ?

Best regards,

Carlos

[Jeffrey Zhang (jeffrey4l)]

Carlos,

You do it wrong. In the neutron_linux_agent container, you has no permission to operator the
namespace. Because you are the *neutron* user.

there is two ways you can do this:

1. enter the container with root user permission
docker exec -u root -it neutron_linuxbridge_agent bash

2. access the namespace in the host machine like the normal way. Kolla now support this and this
     is recommended.

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/302721
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=eec09486a37299edb7c18b8d3345c164c338ba55
Submitter: Jenkins
Branch: master

commit eec09486a37299edb7c18b8d3345c164c338ba55
Author: Jeffrey Zhang <[e-mail]>
Date: Fri Apr 8 23:45:50 2016 +0800

    Fix launch vm failed in neutron-linuxbridge-agent env

    Fix following two issues

    * neutron-linuxbridge-agent container lacks bridge-utils package
    * neutron-dhcp-agent container lacks dnsmasq-utils

    Co-Authored-By: Manjeet Singh Bhatia <email address hidden>
    Closes-Bug: #1567406
    Change-Id: I93a445b06612671f0331cd94573da41d2d3b60a0

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/304951
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=a494219c46c276495bb40f7e524111249429a008
Submitter: Jenkins
Branch: stable/mitaka

commit a494219c46c276495bb40f7e524111249429a008
Author: Jeffrey Zhang <[e-mail]>
Date: Fri Apr 8 23:45:50 2016 +0800

    Fix launch vm failed in neutron-linuxbridge-agent env

    Fix following two issues

    * neutron-linuxbridge-agent container lacks bridge-utils package
    * neutron-dhcp-agent container lacks dnsmasq-utils

    Co-Authored-By: Manjeet Singh Bhatia <email address hidden>
    Closes-Bug: #1567406
    Change-Id: I93a445b06612671f0331cd94573da41d2d3b60a0
    (cherry picked from commit eec09486a37299edb7c18b8d3345c164c338ba55)

[Davanum Srinivas (DIMS) (dims-v)]

This issue was fixed in the openstack/kolla 2.0.0.0rc4 release candidate.

[Doug Hellmann (doug-hellmann)]

This issue was fixed in the openstack/kolla 2.0.0 release.

[Doug Hellmann (doug-hellmann)]

This issue was fixed in the openstack/kolla 1.1.0 release.

[Doug Hellmann (doug-hellmann)]

This issue was fixed in the openstack/kolla 3.0.0.0b1 development milestone.