Avahi is not covered by field sla, so unsubscribing field-high
--
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 ab
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
** Tags added: cdo-qa
** Tags added: foundations-engine
--
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 th
Can you please give me more information about the environments this is
failing in?
(1) Are these production or testing deployments
(2) Is it being installed to a container or a VM
(3) Can you give me the full /var/log/syslog from the example case shown in
the description or another reproductio
Subscribed to field-high as this is causing a lot of failures lately.
--
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 notificat
In the previous package removal, we are seeing:
[10.244.40.30] out: Purging configuration files for avahi-daemon
(0.7-3.1ubuntu1.1) ...
[10.244.40.30] out: rmdir: failed to remove '/var/run/avahi-daemon': Directory
not empty
--
You received this bug notification because you are a member of Ubu
