1) Testing 2) No, it's in baremetal 3) Attached. 4) The machine was deployed with maas - it's a bionic cloud image. We then install/configure maas, run some tests, and remove maas via purge, and repeat. This shows up sometimes on deployments after the initial one - avahi-daemon, or at least its pid file, is left in /var/run/avahi-daemon from a previous run. There are LOTS of commands run. The important ones seem like:
1) apt-get -q install -y avahi-utils maas-region-api maas-dns 2) apt-get -q autoremove --purge maas-common -y 3) apt-get -q autoremove --purge avahi-daemon -y ... repeat until failure ** Attachment added: "syslog" https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1792978/+attachment/5247981/+files/syslog ** Changed in: avahi (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1792978 Title: initscript avahi-daemon, action "start" failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1792978/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
