If maas-enlist fails to reach a DNS server, the node will be named ";; connection timed out; no servers could be reached"
Bug #1081660 reported by
Raphaël Badin
This bug affects 10 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
Critical
|
Andres Rodriguez | ||
maas-enlist (Ubuntu) |
Invalid
|
Critical
|
Andres Rodriguez |
Bug Description
Maybe having a network without a proper DNS setup is wrong, but maas-enlist could definitely deal with that more gracefully.
no longer affects: | maas |
Changed in maas-enlist (Ubuntu): | |
status: | New → Triaged |
importance: | Undecided → Critical |
Changed in maas-enlist (Ubuntu): | |
assignee: | nobody → Andres Rodriguez (andreserl) |
Changed in maas-enlist (Ubuntu): | |
status: | Triaged → Confirmed |
Changed in maas: | |
milestone: | 1.6.0 → 1.6.1 |
Changed in maas: | |
status: | Triaged → Fix Committed |
Changed in maas: | |
assignee: | nobody → Andres Rodriguez (andreserl) |
Changed in maas: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
This bug appears only when using precise daily images.