Neutron DHCP L3 metadata agents restarted on ml2 config change

[Bertrand Lallau]

On ml2_conf.ini config file modification all Neutron agents are actually restarted.
This behaviour is incorrect cause Neutron agents (DHCP, L3,..) should not be ML2 (network layer 2) dependant.

Steps to reproduce bug:
1. change ml2_conf.ini config file
2. launch reconfigure (kolla-ansible reconfigure)
=> all Neutron agents are restarted

Only Neutron plugin Openvswitch agent should be restarted.

[OpenStack Infra (hudson-openstack)]

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

[shaofeng cheng (shaofeng-cheng)]

https://review.openstack.org/#/c/447992/

[OpenStack Infra (hudson-openstack)]

Change abandoned by shaofeng cheng (<email address hidden>) on branch: master
Review: https://review.openstack.org/452403

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/447992
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=5fe11a8fcb302dfd3d52819136a8644921ee1ddc
Submitter: Jenkins
Branch: master

commit 5fe11a8fcb302dfd3d52819136a8644921ee1ddc
Author: Bertrand Lallau <email address hidden>
Date: Tue Mar 21 11:00:11 2017 +0100

    Fix neutron agents restarted on ml2 config change

    The following Neutron agents:
    - neutron-metadata
    - neutron-dhcp-agent
    - neutron-l3-agent
    - neutron-lbaasv2-agent
    - neutron-vpn-agent
    doesn't require ml2_conf.ini file.
    ml2_conf.ini file is used to managed L2 network configuration.
    This config doesn't have to be in DHCP, L3, metadata agents...

    We should remove it to avoid restarting these agents in case of
    ml2_conf.ini file modification.
    Only neutron-server, neutron-openvswitch-agent,
    neutron-linuxbridge-agent must be restarted.

    Closes-Bug: #1677163
    Change-Id: I0876b8a3845d1c2bccd996426a65df1a3a6f7085

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/kolla-ansible 5.0.0.0b2 development milestone.

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/477218
Committed: https://git.openstack.org/cgit/openstack/kolla-ansible/commit/?id=e82c5090c6114297cd8ea722b157e17ad335f365
Submitter: Jenkins
Branch: stable/ocata

commit e82c5090c6114297cd8ea722b157e17ad335f365
Author: Bertrand Lallau <email address hidden>
Date: Tue Mar 21 11:00:11 2017 +0100

    Fix neutron agents restarted on ml2 config change

    The following Neutron agents:
    - neutron-metadata
    - neutron-dhcp-agent
    - neutron-l3-agent
    - neutron-lbaasv2-agent
    - neutron-vpn-agent
    doesn't require ml2_conf.ini file.
    ml2_conf.ini file is used to managed L2 network configuration.
    This config doesn't have to be in DHCP, L3, metadata agents...

    We should remove it to avoid restarting these agents in case of
    ml2_conf.ini file modification.
    Only neutron-server, neutron-openvswitch-agent,
    neutron-linuxbridge-agent must be restarted.

    Closes-Bug: #1677163
    Change-Id: I0876b8a3845d1c2bccd996426a65df1a3a6f7085
    (cherry picked from commit 5fe11a8fcb302dfd3d52819136a8644921ee1ddc)

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/kolla-ansible 4.0.3 release.