Open jianjuns opened 4 months ago
This issue is probably caused by systemd-resolved. Adding a static dns server in /etc/systemd/resolved.conf
fixes it.
[Resolve]
DNS=192.168.1.254
Hi @meibensteiner , thanks for the update, systemd-resolved will update /etc/resolv.conf
whenever there is a change in network configuration, DNS settings, or when the service is restarted or reloaded. You can try to run chattr +i /etc/resolv.conf
command to make the file immutable to avoid the file being modified again.
@jianjuns Looks like the issue is not directly with Antrea secondary network feature but systemd-resolved, considering there are several processes can modify the file, I feel it may not be easy to check from Antrea side, any suggestion for next step?
But do we know why systemd removed the DNS config? We need to understand if that is because of OVS (e.g. systemd/network manager do not recognize interfaces on the OVS even we keep the original host interface names).
Sure, I can check if this can be reproduced locally first.
No chance to take a look at this recently, assigning this to @hongliangl to move forward.
Describe the bug In a secondary network test by @meibensteiner, after the node's primary interface is moved to the secondary OVS bridge, the node lost its DNS config in /etc/resolv.conf.
It may be an interoperability issue with NetworkManager.
To Reproduce
Versions: It happened in cluster with both Ubuntu 24.04 and Debian 12 nodes.