To Reproduce Steps to reproduce the behavior:

1. openstackcontrolplane dnsmasq-dns service pods keeps restarting
   ~~~
   $ oc get pod -l service=dnsmasq
   NAME READY STATUS RESTARTS AGE
   dnsmasq-dns-55657c7658-9v6jj 1/1 Running 23 (6h14m ago) 11d
   dnsmasq-dns-55657c7658-b9pc4 1/1 Running 23 (6h14m ago) 11d
   dnsmasq-dns-55657c7658-nmz8l 1/1 Running 24 (6h15m ago) 11d
   ~~~
2. az1-worker1 - journalctl_--no-pager
3. ~~~
   Sep 16 00:01:19 az1-worker1.-auh1-1.systems kubenswrapper[6982]: I0916 00:01:19.730409    6982 prober.go:107] "Probe failed" probeType="Liveness" pod="openstack/dnsmasq-dns-55657c7658-nmz8l" podUID="5238f6ad-c2b7-4b23-912e-0a6529a176ec" containerName="dnsmasq-dns" probeResult="failure" output="dial tcp 172.x:5353: i/o timeout"
   Sep 16 00:01:19 az1-worker1.-auh1-1.systems kubenswrapper[6982]: I0916 00:01:19.730439    6982 prober.go:107] "Probe failed" probeType="Readiness" pod="openstack/dnsmasq-dns-55657c7658-nmz8l" podUID="5238f6ad-c2b7-4b23-912e-0a6529a176ec" containerName="dnsmasq-dns" probeResult="failure" output="dial tcp 172.x:5353: i/o timeout"
   Sep 16 00:01:19 az1-worker1.-auh1-1.systems kubenswrapper[6982]: I0916 00:01:19.730485    6982 kubelet.go:2542] "SyncLoop (probe)" probe="liveness" status="unhealthy" pod="openstack/dnsmasq-dns-55657c7658-nmz8l"
   Sep 16 00:01:19 az1-worker1.-auh1-1.systems kubenswrapper[6982]: I0916 00:01:19.730540    6982 kubelet.go:2542] "SyncLoop (probe)" probe="readiness" status="" pod="openstack/dnsmasq-dns-55657c7658-nmz8l"
   Sep 16 00:01:19 az1-worker1.-auh1-1.systems kubenswrapper[6982]: I0916 00:01:19.731570    6982 kuberuntime_manager.go:1027] "Message for Container of pod" containerName="dnsmasq-dns" containerStatusID={"Type":"cri-o","ID":"9db824881db7f291c3e782033a78108351a7e68eb103baca2a065947aeb97818"} pod="openstack/dnsmasq-dns-55657c7658-nmz8l" containerMessage="Container dnsmasq-dns failed liveness probe, will be restarted"
   Sep 16 00:01:19 az1-worker1.ae-auh1-1.systems kubenswrapper[6982]: I0916 00:01:19.731631    6982 kuberuntime_container.go:808] "Killing container with a grace period" pod="openstack/dnsmasq-dns-55657c7658-nmz8l" podUID="5238f6ad-c2b7-4b23-912e-0a6529a176ec" containerName="dnsmasq-dns" containerID="cri-o://9db824881db7f291c3e782033a78108351a7e68eb103baca2a065947aeb97818" gracePeriod=10
   Sep 16 00:01:19 az1-worker1.os.ae-auh1-1.systems crio[6711]: time="2025-09-16 00:01:19.731977904Z" level=info msg="Stopping container: 9db824881db7f291c3e782033a78108351a7e68eb103baca2a065947aeb97818 (timeout: 10s)" id=8d1a9daa-055d-4cb3-a213-880168a9bbf7 name=/runtime.v1.RuntimeService/StopContainer
4. ~~~

Expected behavior

• Should not restart

Device Info (please complete the following information):

• openstack-operators: 1.0.9
• OPENSTACK_RELEASE_VERSION: 18.0.7-20250408.2

Bug impact

• It seems there is no impact so far

Known workaround

• The pods restart by themselves