SEAPATH Yocto dnsmasq.service fail on boot after configuration

[Revalioli]

On SEAPATH Yocto, libvirt installs as dependency dnsmasq. dnsmasq.service is then started along libvirtd at boot and requires /etc/resolv.conf to exist, or be a link to an existing file.

Currently, role network_resolved disable systemd-resolved.service if dns_servers isn't defined.
But if systemd-resolved.service isn't started, then resolv.conf is never created, and dnsmasq.service fails because /etc/resolv.conf points to nothing. This makes one cukinia test to fail.

If I understood correctly, dnsmasq isn't installed on SEAPATH Debian.
How should both flavors be harmonized regarding dnsmasq and systemd-resolved configuration ? @eroussy @insatomcat @dupremathieu

• Installing dnsmasq on Debian and keeping dnsmasq and systemd-resolved services enabled even without dns-servers specified in the ansible inventory ?
• Remove dnsmasq from SEAPATH Yocto ? In Yocto, the libvirt recipe requires dnsmasq to build, so would have to uncouple dnsmasq from libvirt.
• Something else ?

As a temporary workaround, I opened a PR #720 to keep systemd-resolved.service enabled on SEAPATH Yocto.

To Reproduce
Steps to reproduce the behavior:

1. Build and flash a Yocto image (standalone or cluster)
2. Configure the system with Ansible without defining dns_servers
3. Reboot and run systemctl status systemd-resolved

[Revalioli]

Related issue : seapath/meta-seapath#301