maas-server setting requires port even when using http default

Bug #972829 reported by Gavin Panella
50
This bug affects 10 people
Affects Status Importance Assigned to Milestone
pyjuju
Fix Released
Low
Julian Edwards
juju (Ubuntu)
Fix Released
Low
Unassigned
Precise
Won't Fix
Low
Unassigned

Bug Description

[Test Case]
1. setup MaaS listening on port 80
2. setup a juju environment in ~/.juju/environments.yaml with type: maas and maas-server: "http://yourmaas/"
3. Run juju bootstrap. If affected, an error will be printed due to missing port. Fixed versions will contact maas on port 80.

[Regression Potential]
The code change is very small and there are regression tests for the specific code path so there is very little regression potential, though the maas provider should be smoke tested to make sure everything still works as expected.

[Original Description]
maas-server must be specified as "http://maas.example.com:80/"; "http://maas.example.com/" is not enough. I would expect to be able to omit the port specification when using the scheme's default port.

Related branches

Changed in juju:
status: New → In Progress
assignee: nobody → Julian Edwards (julian-edwards)
Changed in juju:
milestone: none → galapagos
importance: Undecided → Low
Changed in juju:
status: In Progress → Fix Released
Changed in juju (Ubuntu):
status: New → Triaged
importance: Undecided → Low
Changed in juju (Ubuntu Precise):
status: New → Triaged
importance: Undecided → Low
description: updated
Changed in juju (Ubuntu):
status: Triaged → Fix Released
Changed in juju (Ubuntu Precise):
status: Triaged → Fix Released
status: Fix Released → Triaged
Revision history for this message
Julian Edwards (julian-edwards) wrote :

Can someone please SRU this fix to precise? It is causing a lot of problems for people.

Revision history for this message
Max (mattrulz127) wrote :

+1 for this, I just spent ~8 hours variously trying to pin down the issue, up to and including reinstalling the entire MAAS environment a few times, before eventually coming across this bug and figuring out the issue. Please fix!

Revision history for this message
Steve Langasek (vorlon) wrote :

The Precise Pangolin has reached end of life, so this bug will not be fixed for that release

Changed in juju (Ubuntu Precise):
status: Triaged → Won't Fix
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.