Unable to deploy xenial on MAAS / resolv.conf not populated
Bug #1553017 reported by
Cheryl Jennings
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
open-iscsi (Ubuntu) |
Fix Released
|
High
|
Scott Moser |
Bug Description
When trying to deploy a Xenial node on MAAS, the node quickly transitions from "Deploying" to "Failed Deployment".
Connecting to the console shows that cloud init continues to run, and the node will eventually get to a login screen, but I cannot access the machine over the network.
This has been seen on MAAS 1.9.1 and 1.10.
Related bugs:
* Bug 1050487: resolvconf not updated on iscsi root
* Bug 1463461: resolvconf not updated by /lib/systemd/
* Bug 1501033: transient error results in /etc/resolv.conf not populated in iscsi root
summary: |
- Unable to deploy xenial on MAAS + Unable to deploy xenial on MAAS / resolv.conf not populated |
Changed in open-iscsi (Ubuntu): | |
importance: | Undecided → High |
To post a comment you must log in.
Cloud-init output from roaksoax: http:// pastebin. ubuntu. com/15278513/