MAAS not sending correct metadata_url
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
Medium
|
Alberto Donato | ||
3.2 |
Fix Released
|
Critical
|
Alberto Donato |
Bug Description
Hello,
I tried to install a new region controller and decided to install the latest version of MAAS (3.2). I tried to commission a node it didnt work! I got this message:
cloudinit.
So I did a network capture and figured out the metadata url was wrong:
in 3.2: metadata_url: http://
So I removed MAAS 3.2, did install 3.0 and got the correct metadata_url:
3.0: metadata_url: http://
Then I tried to install 3.0 then upgrade to 3.2 (not directly install 3.2) and got the same problem. Do you think the problem could fix itself by using FQDN instead of IP address?
Best regards,
Related branches
- Alberto Donato (community): Approve
-
Diff: 163 lines (+101/-21)2 files modifiedsrc/maasserver/compose_preseed.py (+23/-17)
src/maasserver/tests/test_compose_preseed.py (+78/-4)
- Adam Collard (community): Approve
- MAAS Lander: Approve
-
Diff: 163 lines (+101/-21)2 files modifiedsrc/maasserver/compose_preseed.py (+23/-17)
src/maasserver/tests/test_compose_preseed.py (+78/-4)
Changed in maas: | |
status: | New → Triaged |
importance: | Undecided → Medium |
tags: | added: bug-council |
Changed in maas: | |
milestone: | none → 3.3.0 |
Changed in maas: | |
status: | Triaged → In Progress |
assignee: | nobody → Alberto Donato (ack) |
Changed in maas: | |
status: | In Progress → Fix Committed |
Changed in maas: | |
status: | Fix Committed → Fix Released |
status: | Fix Released → Fix Committed |
Changed in maas: | |
milestone: | 3.3.0 → 3.3.0-beta1 |
Changed in maas: | |
status: | Fix Committed → Fix Released |
Are you using the MAAS server for DNS resolution on the nodes you are commissioning? As I believe it should be able to resolve that metadata_url.