[2.4] maas_url http://<ip>:5240/MAAS in regiond.conf leads to invalid metadata URL

Bug #1761314 reported by Stéphane Graber
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Fix Released
High
Unassigned

Bug Description

With /etc/maas/rackd.conf containing maas_url: http://localhost:5240/MAAS, I end up with cloud-config-url=//172.17.16.10/MAAS/metadta/latest/... passed to my system on the command line. This isn't a valid URL and prevents deploy.

Updating rackd.conf to use http://172.17.16.10:5240/MAAS instead fixes this.

That's on MAAS 2.4 beta1:
root@maas01:/var/log/maas/rsyslog/vm10/2018-04-04# dpkg -l | grep maas
ii maas 2.4.0~beta1-6799-g391e5f16d-0ubuntu1 all "Metal as a Service" is a physical cloud and IPAM
ii maas-cli 2.4.0~beta1-6799-g391e5f16d-0ubuntu1 all MAAS client and command-line interface
ii maas-common 2.4.0~beta1-6799-g391e5f16d-0ubuntu1 all MAAS server common files
ii maas-dhcp 2.4.0~beta1-6799-g391e5f16d-0ubuntu1 all MAAS DHCP server
ii maas-proxy 2.4.0~beta1-6799-g391e5f16d-0ubuntu1 all MAAS Caching Proxy
ii maas-rack-controller 2.4.0~beta1-6799-g391e5f16d-0ubuntu1 all Rack Controller for MAAS
ii maas-region-api 2.4.0~beta1-6799-g391e5f16d-0ubuntu1 all Region controller API service for MAAS
ii maas-region-controller 2.4.0~beta1-6799-g391e5f16d-0ubuntu1 all Region Controller for MAAS
ii python3-django-maas 2.4.0~beta1-6799-g391e5f16d-0ubuntu1 all MAAS server Django web framework (Python 3)
ii python3-maas-client 2.4.0~beta1-6799-g391e5f16d-0ubuntu1 all MAAS python API client (Python 3)
ii python3-maas-provisioningserver 2.4.0~beta1-6799-g391e5f16d-0ubuntu1 all MAAS server provisioning libraries (Python 3)

Revision history for this message
Andres Rodriguez (andreserl) wrote :

From IRC discussion:

1. /etc/maas/regiond.conf:maas_url was http://<ip>/MAAS
2. /etc/maas/rackd.conf:maas_url was http://localhost:5240/MAAS
3. /etc/maas/regiond.conf was updated to http://<ip>:5240/MAAS & /etc/maas/rackd.conf was left as http://localhost:5240/MAAS
4. restart maas-regiond
5. cloud-config-url was still incorrect, pointing to http://<ip>/MAAS as per the above bug.

To solve:

6. /etc/maas/rackd.conf:maas_url http://<ip>:5240/MAAS fixed it.

summary: - maas_url of http://localhost:5240/MAAS in rackd.conf leads to invalid
+ [2.4] maas_url http://<ip>:5240/MAAS in regiond.conf leads to invalid
metadata URL
no longer affects: maas (Ubuntu)
Changed in maas:
milestone: none → 2.4.0beta2
importance: Undecided → High
status: New → Triaged
Changed in maas:
assignee: nobody → Blake Rouse (blake-rouse)
Changed in maas:
assignee: Blake Rouse (blake-rouse) → Mike Pontillo (mpontillo)
Revision history for this message
Andres Rodriguez (andreserl) wrote :

In this case:

 cloud-config-url=//172.17.16.10/MAAS/metadta/latest/

Changed in maas:
milestone: 2.4.0beta2 → 2.4.0rc1
Changed in maas:
milestone: 2.4.0rc1 → 2.4.0rc2
assignee: Mike Pontillo (mpontillo) → nobody
Revision history for this message
Andres Rodriguez (andreserl) wrote :

This may be already fixed on b3, so marking it as incomplete in the meantime.

Changed in maas:
status: Triaged → Incomplete
Revision history for this message
Stéphane Graber (stgraber) wrote :

Haven't run into this in a while so let's assume it has been fixed.

Changed in maas:
status: Incomplete → Fix Released
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.