Ensure "keepalived" is correctly disabled (the process does not exist)

[Rodolfo Alonso]

Ensure "keepalived" is correctly disabled, that means the process does not exist. Currently the process is terminated sending a SIGTERM signal [1]. If that fails, for any reason, the "keepalived" process will continue running. For example in [2][3]: the SIGTERM signal is sent but the process is still running ("psutil.Process(pid)" is able to retrieve the process information).

[1]https://github.com/openstack/neutron/blob/28c79c9747a3031a0d1321199d2d72336e4076ed/neutron/agent/linux/keepalived.py#L475-L480
[2]https://be8bc338a39cf869db17-e8a1a74829c12f710e3c5d0fa3d85b60.ssl.cf1.rackcdn.com/763231/10/check/neutron-functional-with-uwsgi/db6a5a3/controller/logs/dsvm-functional-logs/neutron.tests.functional.agent.l3.extensions.test_gateway_ip_qos_extension.TestRouterGatewayIPQosAgentExtensionDVR.test_dvr_router_lifecycle_ha_with_snat_with_fips.txt
[3]http://paste.openstack.org/show/801003/

[Slawek Kaplonski (slaweq)]

Patch https://review.opendev.org/c/openstack/neutron/+/766939

[Rodolfo Alonso (rodolfo-alonso-hernandez)]

Patch: https://review.opendev.org/c/openstack/neutron/+/766939

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/neutron 15.3.1 release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/neutron 16.3.0 release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/neutron 17.1.0 release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/neutron 18.0.0.0rc1 release candidate.