MAAS ephemeral boot environments should include the system hostname in /etc/hosts
Bug #1670444 reported by
Mike Pontillo
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
Low
|
Lee Trager |
Bug Description
Due to a bug involving interaction with Juju, MAAS does not currently tell cloud-init to manage /etc/hosts. This prevents Juju charms trying to find our the local IP address from obtaining "127.0.1.1" as the value when looking up the hostname.
However, during ephemeral MAAS boots (such as commissioning, testing, or initial deployment), this can cause large delays during commissioning if the configured DNS server cannot resolve the node, since the DNS request might time out every time `sudo` runs.
Workaround: ephemeral MAAS boots should always execute a command such as this:
echo "127.0.1.1 $(hostname)" >> /etc/hosts
Note that this should NOT appear in /etc/hosts post-deployment.
Related branches
lp:~ltrager/maas/fix_ephemeral_sudo
- Mike Pontillo (community): Approve
- Andres Rodriguez (community): Needs Fixing
-
Diff: 52 lines (+24/-0)2 files modifiedsrc/maasserver/compose_preseed.py (+7/-0)
src/maasserver/tests/test_compose_preseed.py (+17/-0)
Changed in maas: | |
importance: | Undecided → Low |
milestone: | none → 2.2.0 |
status: | New → Triaged |
Changed in maas: | |
assignee: | nobody → Lee Trager (ltrager) |
status: | Triaged → In Progress |
Changed in maas: | |
status: | In Progress → Fix Committed |
Changed in maas: | |
milestone: | 2.2.0 → 2.2.0rc1 |
Changed in maas: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.