neutron-fwaas ships /usr/bin/neutron-l3-agent a 2nd time

[Thomas Goirand]

In distributions, it's not possible to ship twice a daemon in /usr/bin with 2 different packages. This means that /usr/bin/neutron-l3-agent in neutron-fwaas is clashing with /usr/bin/neutron-l3-agent from python-neutron. In Debian, we will rename /usr/bin/neutron-l3-agent as /usr/bin/neutron-fwaas-l3-agent. Please do the same upstream.

Full explanations on why this is a problem is available here:
http://lists.openstack.org/pipermail/openstack-dev/2016-June/097956.html

I'm available on IRC if you want to discuss the problem as well.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Change abandoned by Haifeng Yan (<email address hidden>) on branch: master
Review: https://review.openstack.org/337988
Reason: maitain in neutron-fwaas devstack plugin

[OpenStack Infra (hudson-openstack)]

Change abandoned by Haifeng Yan (<email address hidden>) on branch: master
Review: https://review.openstack.org/337402
Reason: fwaas will act as a L3 agent extension, the patch doesn't align the design.

[Ihar Hrachyshka (ihar-hrachyshka)]

The fact that we don't just rename the agent but introduce an extension does not make the bug invalid. Moving back to Confirmed.

[Reedip (reedip-banerjee-deactivatedaccount)]

Is it still an issue ?

[Bernard Cafarelli (bcafarel)]

This was fixed in 2016/08 with the switch to L3 agent extension:
https://github.com/openstack/neutron-fwaas/commit/6718fd85603c77f7f36a1b74954696af47f13c94#diff-2373269afd0ff20523b0414451251696