When attempting to bootstrap via MAAS we hit this error:
(conjure-dev) 1 ubuntu@brucewillis:~⟫ JUJU_LOGGING_CONFIG="<root>=TRACE" juju --debug bootstrap sparkle maas/battlemidget.lol:5240 --upload-tools --config image-stream=daily --config enable-os-upgrade=false --bootstrap-series=xenial --credential sparkle
2016-07-07 18:57:10 INFO juju.cmd supercommand.go:63 running juju [2.0-beta11.4111 gc go1.6.2]
2016-07-07 18:57:10 INFO cmd cmd.go:141 cloud "maas" not found, trying as a provider name
2016-07-07 18:57:10 INFO cmd cmd.go:141 interpreting %q as the cloud endpoint
2016-07-07 18:57:10 DEBUG juju.cmd.juju.commands bootstrap.go:445 preparing controller with config: map[type:maas name:controller uuid:b03a5ab1-66c8-4955-8882-120f7d3dc099 image-stream:daily enable-os-upgrade:false]
2016-07-07 18:57:10 DEBUG juju.provider.maas environprovider.go:32 opening model "controller".
2016-07-07 18:57:10 ERROR cmd supercommand.go:458 malformed maas-server URL 'battlemidget.lol:5240': %!s(<nil>)
2016-07-07 18:57:10 DEBUG cmd supercommand.go:459 (error details: [{github.com/juju/juju/cmd/juju/commands/bootstrap.go:504: } {github.com/juju/juju/environs/open.go:108: } {github.com/juju/juju/environs/open.go:194: } {github.com/juju/juju/provider/maas/environ.go:189:
} {malformed maas-server URL 'battlemidget.lol:5240': %!s(<nil>)}])
MAAS doesn't assume port 80 is always available so having access to set the port of the actual MAAS web application is usually beneficial.
Hi Cheryl,
This needs to be critical because MAAS no longer offers port 80 (we only do for backwards compatibility), but MAAS binds to port 5240.