From 0f9de5e20c996ef231db505bbe18402c1ea7021e Mon Sep 17 00:00:00 2001 From: Ahmed Abdelhalim Date: Thu, 21 Aug 2025 03:24:34 +0200 Subject: Fix the wireguard install The conflict was due to resolvconf was removing the systemd-resolved configuration and that was causing the network to go down and the fallback on the statically managed resolv.conf (which wasn't able to resolve the DNS) due to how network manager requiring the DNS resolution to happen through systemd-resolved --- roles/network/tasks/main.yml | 6 ------ 1 file changed, 6 deletions(-) (limited to 'roles/network') diff --git a/roles/network/tasks/main.yml b/roles/network/tasks/main.yml index fd2553ff..c8c48268 100644 --- a/roles/network/tasks/main.yml +++ b/roles/network/tasks/main.yml @@ -54,12 +54,6 @@ - "Restart NetworkManager" - "Restart systemd-resolved" block: - - name: "Remove resolv.conf symlink" - ansible.builtin.file: - path: "/etc/resolv.conf" - state: "absent" - when: not ansible_is_chroot - - name: "Configure systemd-resolved" ansible.builtin.template: src: "resolved.conf.j2" -- cgit v1.2.3