** Description changed: - 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. + [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.
-- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju in Ubuntu. https://bugs.launchpad.net/bugs/972829 Title: maas-server setting requires port even when using http default To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/972829/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
