Invalid resolved.conf on some nodes

[hadi2f244]

What happened?

I just checked /etc/systemd/resolved.conf file in some of my kubernetes cluster. There were two versions!
I've just used kubespray to upgrade, delete and add nodes. There were some situations that kubespray doesn't update /etc/systemd/resolved.conf.

What did you expect to happen?

I expect the /etc/systemd/resolved.conf file content to be the following on all masters and workers:

[Resolve]
DNS=169.254.25.10
FallbackDNS=
Domains=
#LLMNR=no
#MulticastDNS=no
DNSSEC=no
Cache=no-negative
#DNSStubListener=yes

But on some workers I saw this content:

[Resolve]
# Some examples of DNS servers which may be used for DNS= and FallbackDNS=:
# Cloudflare: 1.1.1.1#cloudflare-dns.com 1.0.0.1#cloudflare-dns.com 2606:4700:4700::1111#cloudflare-dns.com 2606:4700:4700::1001#cloudflare-dns.com
# Google:     8.8.8.8#dns.google 8.8.4.4#dns.google 2001:4860:4860::8888#dns.google 2001:4860:4860::8844#dns.google
# Quad9:      9.9.9.9#dns.quad9.net 149.112.112.112#dns.quad9.net 2620:fe::fe#dns.quad9.net 2620:fe::9#dns.quad9.net
#DNS=
#FallbackDNS=
#Domains=
#DNSSEC=no
#DNSOverTLS=no
#MulticastDNS=no
#LLMNR=no
#Cache=no-negative
#CacheFromLocalhost=no
#DNSStubListener=yes
#DNSStubListenerExtra=
#ReadEtcHosts=yes
#ResolveUnicastSingleLabel=no

How can we reproduce it (as minimally and precisely as possible)?

I managed all of my clusters by Kubespray and I saw similar issue on all of them.

OS

Ubuntu 22

Version of Ansible

ansible==9.8.0

Version of Python

Python 3.11.11

Version of Kubespray (commit)

7e0a407

Network plugin used

calico

Full inventory with variables

.

Command used to invoke ansible

N/A

Output of ansible run

N/A

Anything else we need to know

No response

[tico88612]

Are there specific steps to reproduce this? (e.g. inventory? variables?) The information you provided does not help us debug or reproduce.