Systemd-resolved.service

Just a note to reiterate your frustrations @DavidFW1960 - these automatic supervisor updates have a habit of borking the supervised installation on my system with neither warning nor documentation. I try to behave well and keep up with the latest docs on how to stay “supported”, but it’s not enough. My system dies anyway because a supervisor update fails. The annoying thing is that sometimes, the full impact of a failed update might not show up until I next reboot my box, which can be days or weeks.

As described in this post, I’ve become pretty quick at rebuilding my installation - it seems to be the quickest way to bring a supervised installation back from the dead.

I’d love it if the wonderful HA team could put a bit more effort into notifying of upcoming changes to supervisor that might break supervised installations.