maas-server setting requires port even when using http default
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/
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://
Related branches
- Kapil Thangavelu (community): Approve
- William Reade (community): Approve
-
Diff: 55 lines (+36/-1)2 files modifiedjuju/providers/maas/auth.py (+7/-1)
juju/providers/maas/tests/test_maas.py (+29/-0)
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 |
Can someone please SRU this fix to precise? It is causing a lot of problems for people.