Once we've removed network.target from wanted targets for
mariadbcheck.socket, it started to fail to startup intermitently in LXC
deployments, since it was trying to bind on IP address that is not
brought up yet. At the same time we can't wait for IP being up, as
OVS while providing network, waits for socket.target as it needs
to have ovsdb started up, so waiting for network.target does
create circular dependency.
To avoid that we're allowing socket to bind on IP even when IP is not
UP yet. Other possible solution would be to bind on 0.0.0.0.
Reviewed: https:/ /review. opendev. org/c/openstack /openstack- ansible- galera_ server/ +/874733 /opendev. org/openstack/ openstack- ansible- galera_ server/ commit/ 4acaf657873452e 0720a1b3f5ba2f8 89ab88d96e
Committed: https:/
Submitter: "Zuul (22348)"
Branch: stable/yoga
commit 4acaf657873452e 0720a1b3f5ba2f8 89ab88d96e
Author: Dmitriy Rabotyagov <email address hidden>
Date: Thu Feb 9 22:19:36 2023 +0100
Allow maridbcheck socket to FreeBind
Once we've removed network.target from wanted targets for k.socket, it started to fail to startup intermitently in LXC
mariadbchec
deployments, since it was trying to bind on IP address that is not
brought up yet. At the same time we can't wait for IP being up, as
OVS while providing network, waits for socket.target as it needs
to have ovsdb started up, so waiting for network.target does
create circular dependency.
To avoid that we're allowing socket to bind on IP even when IP is not
UP yet. Other possible solution would be to bind on 0.0.0.0.
Depends-On: https:/ /review. opendev. org/c/openstack /openstack- ansible/ +/872896 8419d261cd94e30 17523177142 695e33568318464 66f6991089)
Change-Id: Ia4cde2153813e6
Closes-Bug: #2003631
Related-Bug: #2002653
(cherry picked from commit 8a8d29ea490fba6