[2.3.0] metadat URL is [::1] when no port is specified for ipv4 IP in rackd.conf

Bug #1757991 reported by Jeff Hillman
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Fix Released
High
Unassigned
2.3
Won't Fix
High
Unassigned

Bug Description

MAAS 2.3.0
Xenial 16.04.3

When adding a rack controller to an existing region controlelr either via 'maas-rack register' and specifying http://a.b.c.d/MASS OR just editing /etc/maas/rackd.conf and setting the URL to http;//a.b.c.d/MASS, causes the metadata URL provided during commssioning to be http://[::1]:5240/MAAS.

To resolved this, either register with http://a.b.c.d:5240/MAAS or edit the URL in /etc/maas/rackd.conf to be http://a.b.c.d:5240/MAAS.

Basically, if you do not specify a port with an IPv4 address to the rack controller, then it will assume IPv6 with the 5240 port to provide a metadata URL.

Tags: cpe-onsite
Revision history for this message
Jeff Hillman (jhillman) wrote :
Revision history for this message
Jeff Hillman (jhillman) wrote :
Revision history for this message
Andres Rodriguez (andreserl) wrote :

Thanks for the bug.

The one thing we need to verify is whether this is also present in 2.3.1, as Mike believes it should have been fixed then.

However, we have seen this issue when rackd.conf was pointing to localhost.

Changed in maas:
importance: Undecided → High
no longer affects: maas/2.4
Changed in maas:
milestone: none → 2.4.0beta1
Lee Trager (ltrager)
Changed in maas:
status: New → Triaged
Changed in maas:
milestone: 2.4.0beta1 → 2.4.0beta2
Changed in maas:
milestone: 2.4.0beta2 → 2.4.0beta3
milestone: 2.4.0beta3 → 2.4.0beta2
Changed in maas:
assignee: nobody → Mike Pontillo (mpontillo)
Revision history for this message
Andres Rodriguez (andreserl) wrote :

In this case:

cloud-config-url=http://[::1]:5240/MAAS/metadata/....

Changed in maas:
milestone: 2.4.0beta2 → 2.4.0rc1
Changed in maas:
milestone: 2.4.0rc1 → 2.4.0rc2
Changed in maas:
status: Triaged → Incomplete
Revision history for this message
Andres Rodriguez (andreserl) wrote :

We believe this issue has now been fixed in the latest MAAS release, as part of the proxying through the rack feature.

If you believe this issue is still present in 2.3 and/or is affecting users, please re-open the 2.3 bug task. (I'll mark it as wontfix)

Changed in maas:
milestone: 2.4.0rc2 → 2.5.0
status: Incomplete → Fix Released
assignee: Mike Pontillo (mpontillo) → nobody
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.