Comment 2 for bug 2003631

Revision history for this message
Jose Gaitan (vchjgaitan) wrote (last edit ):

Hello Dmitriy,

I appreciate your prompt response to this issue. Unfortunately, I do not think this is related to the network.target being removed from the systemd unit. I noticed the change from commit If4729eca992a0e647e2f15b3d77ad6300bbf9c12 to remove the network.target from the mariadbcheck.socket unit was merged on January 13, 2023. In turn, our Openstack-Ansible deployment that is generating this issue was pulled and bootstrapped from the stable/zed repo on January 20, 2023.

Additionally, after looking into the /etc/systemd/system/mariadbcheck.socket unit file in all three Galera LXC containers we confirmed the network.target is not included as a dependency, which indicates the patch from commit If4729eca992a0e647e2f15b3d77ad6300bbf9c12 was already applied on this deployment. See file content below:

====
root@inf2-mia-galera-container-3b0c3b78:~# cat /etc/systemd/system/mariadbcheck.socket
# Ansible managed

[Unit]
Description=mariadbcheck socket

[Socket]

ListenStream=10.10.37.209:9200
IPAddressDeny=any
IPAddressAllow=10.10.37.132 10.10.37.209 10.10.39.236 10.10.36.11 10.10.36.12 10.10.36.13 127.0.0.1
Accept=yes

[Install]
WantedBy=sockets.target
====

Out of an abundance of caution, we will rerun the bootstrap-ansible.sh script and test again. We will report back the results.

Thank you,

Roger