[2.1] MAAS rack (and region) should not depend on avahi-utils
Bug #1619493 reported by
LaMont Jones
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Invalid
|
Medium
|
Unassigned |
Bug Description
maas-rack-
2016-09-01 22:41:16 [-] FileNotFoundError: [Errno 2] No such file or directory: '/usr/bin/
If avahi-utils is not installed (and therefore avahi-browse is not present), we should be more graceful about it and not generate a traceback.
A similar thing applies to tcpdump.
summary: |
- rack needs to be more graceful about missing recommends + [2.1] rack needs to be more graceful about missing recommends |
Changed in maas: | |
status: | New → Triaged |
importance: | Undecided → Medium |
milestone: | none → 2.1.0 |
Changed in maas: | |
milestone: | 2.1.0 → 2.1.1 |
Changed in maas: | |
milestone: | 2.1.1 → 2.1.2 |
Changed in maas: | |
milestone: | 2.1.2 → 2.1.3 |
To post a comment you must log in.
We need to change this back to a Recommends (it is currently a Depends, because we're being too honest) and allow MAAS to fail gracefully when avahi isn't installed. I don't think it's proper that we're essentially forcing the avahi service to be installed on any MAAS region or rack controller. (Yes, it improves the MAAS user experience, but customers may have the requirement that avahi not be installed, such as for security reasons.)