avahi not a friend with rhel7.5

[pondrejk]

Just FYI, with vault req. testing I found avahi as installed in automation job fails to start on rhel7.5 (job no 3602). Going to work around this by running automation from a separate branch, but filing this issue as it can cause trouble in the future.

[JacobCallahan]

from my jobs

[mybox] run: service avahi-daemon restart
[mybox] out: Redirecting to /bin/systemctl restart avahi-daemon.service
[mybox] out: Job for avahi-daemon.service failed because the control process exited with error code. See "systemctl status avahi-daemon.service" and "journalctl -xe" for details.
[mybox] out: 

Fatal error: run() received nonzero return code 1 while executing!

from my satellite box

-bash-4.2# systemctl status avahi-daemon.service
● avahi-daemon.service - Avahi mDNS/DNS-SD Stack
   Loaded: loaded (/usr/lib/systemd/system/avahi-daemon.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Tue 2018-04-10 20:56:40 CEST; 7min ago
  Process: 29157 ExecStart=/usr/sbin/avahi-daemon -s (code=exited, status=255)
 Main PID: 29157 (code=exited, status=255)
   Status: "avahi-daemon 0.6.31 exiting."

Apr 10 20:56:40 mybox avahi-daemon[29157]: Found user 'avahi' (UID 70) and group 'avahi' (GID 70).
Apr 10 20:56:40 mybox avahi-daemon[29157]: Successfully dropped root privileges.
Apr 10 20:56:40 mybox avahi-daemon[29157]: avahi-daemon 0.6.31 starting up.
Apr 10 20:56:40 mybox avahi-daemon[29157]: dbus_bus_request_name(): Connection ":1.90" is not allowed to own the service "org.freedesktop.Avahi" d...tion file
Apr 10 20:56:40 mybox avahi-daemon[29157]: WARNING: Failed to contact D-Bus daemon.
Apr 10 20:56:40 mybox avahi-daemon[29157]: avahi-daemon 0.6.31 exiting.
Apr 10 20:56:40 mybox systemd[1]: avahi-daemon.service: main process exited, code=exited, status=255/n/a
Apr 10 20:56:40 mybox systemd[1]: Failed to start Avahi mDNS/DNS-SD Stack.
Apr 10 20:56:40 mybox systemd[1]: Unit avahi-daemon.service entered failed state.
Apr 10 20:56:40 mybox systemd[1]: avahi-daemon.service failed.
Hint: Some lines were ellipsized, use -l to show in full.

[JacobCallahan]

I think this is a possible solution.

systemctl restart dbus
systemctl start avahi-daemon.service

I performed this on my failed satellite box and it looks good.

-bash-4.2# systemctl start avahi-daemon.service

-bash-4.2# systemctl status avahi-daemon.service
● avahi-daemon.service - Avahi mDNS/DNS-SD Stack
   Loaded: loaded (/usr/lib/systemd/system/avahi-daemon.service; enabled; vendor preset: enabled)
   Active: active (running) since Tue 2018-04-10 21:34:41 CEST; 9s ago
 Main PID: 16059 (avahi-daemon)
   Status: "avahi-daemon 0.6.31 starting up."
   CGroup: /system.slice/avahi-daemon.service
           ├─16059 avahi-daemon: running [ibm-x3550m3-10.local]
           └─16060 avahi-daemon: chroot helper

[pgagne]

Why are we installing avahi? @kbidarkar , or anyone know? What thing are we trying to do that we use it for?

[rplevka]

@pgagne,
t's currently being used by vm.py to determine the IP address of a vm after it's created by snap-guest and booted. We do not have a control over the dhcp server

[lpramuk]

@pgagne it is our independent IP discovery service used by automation