MAAS picks the wrong IP for curtin
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
High
|
Unassigned |
Bug Description
We have a cluster with two networks, pub_net and priv_net. For hardware reasons we need to PXE boot of the pub_net, but we still want to use the priv_net for juju.
To accomodate this, we set pub_net to "Manage DHCP" and priv_net to "Manage DHCP and DNS". During curtin run, we notice that curtin tries to download root-tgz from the priv_net side of maas. This fails since that network is not up at this time.
In maasserver.
It would be better if maas would make sure to only pass in an IP for a network that curtin can actually reach.
(you do not want the contents of /var/log/maas/*, it's huge)
dpkg -l '*maas*'|cat
Desired=
| Status=
|/ Err?=(none)
||/ Name Version Architecture Description
+++-===
ii maas 1.7.0+bzr3299-
ii maas-cli 1.7.0+bzr3299-
ii maas-cluster-
ii maas-common 1.7.0+bzr3299-
ii maas-dhcp 1.7.0+bzr3299-
ii maas-dns 1.7.0+bzr3299-
ii maas-proxy 1.7.0+bzr3299-
ii maas-region-
ii maas-region-
ii python-django-maas 1.7.0+bzr3299-
ii python-maas-client 1.7.0+bzr3299-
ii python-
tags: | added: canonical-bootstack canonical-is |
Changed in maas: | |
status: | New → Triaged |
importance: | Undecided → High |
Changed in maas: | |
milestone: | none → next |
Changed in maas: | |
status: | Triaged → Fix Committed |
milestone: | next → 1.9.0 |
Changed in maas: | |
status: | Fix Committed → Fix Released |