Ensure that haproxy spawned by the metadata agents is active
In both neutron-metadata and neutron-ovn-metadata agents we should
ensure that haproxy service spawned for network/router is actually
active before moving on.
This patch adds that check and this is similar to what was already
implemented some time ago for the dnsmasq process spawned by the dhcp
agent.
Related-Bug: #2052787
Change-Id: Ic58640d89952fa03bd1059608ee6c9072fbaabf5
(cherry picked from commit 2f7f7c2fc29d0ac26b5ff9d82867952a40f0fa1b)
Reviewed: https:/ /review. opendev. org/c/openstack /neutron/ +/910308 /opendev. org/openstack/ neutron/ commit/ 32af674783c69c8 7d0feed622434c6 839938a141
Committed: https:/
Submitter: "Zuul (22348)"
Branch: stable/2023.2
commit 32af674783c69c8 7d0feed622434c6 839938a141
Author: Slawek Kaplonski <email address hidden>
Date: Thu Feb 22 10:06:58 2024 +0100
Ensure that haproxy spawned by the metadata agents is active
In both neutron-metadata and neutron- ovn-metadata agents we should
ensure that haproxy service spawned for network/router is actually
active before moving on.
This patch adds that check and this is similar to what was already
implemented some time ago for the dnsmasq process spawned by the dhcp
agent.
Related-Bug: #2052787 03bd1059608ee6c 9072fbaabf5 26b5ff9d8286795 2a40f0fa1b)
Change-Id: Ic58640d89952fa
(cherry picked from commit 2f7f7c2fc29d0ac