Improve add MAAS process

Bug #1908630 reported by Chris Sanders
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Canonical Juju
Triaged
Medium
Unassigned

Bug Description

When trying to add a MAAS instance to juju the boostrap process is not very user friendly. I've done this before, and was trying to add a new MAAS and was surprised how hard it is to get Juju to add MAAS as a new cloud.

This is the full terminal output from my attempts to add MAAS to juju.

$ juju add-cloud
This operation can be applied to both a copy on this client and to the one on a controller.
Do you want to add cloud to:
    1. client only (--client)
    2. controller "prod-maas" only (--controller prod-maas)
    3. both (--client --controller prod-maas)
Enter your choice, or type Q|q to quit: 1
Cloud Types
  lxd
  maas
  manual
  openstack
  vsphere

Select cloud type: maas

Enter a name for your maas cloud: k8s-maas

Enter the API endpoint url: 192.168.1.187
Can't validate endpoint: No MAAS server running at 192.168.1.187

Enter the API endpoint url: 192.168.1.187:5240
Can't validate endpoint: No MAAS server running at 192.168.1.187:5240

Enter the API endpoint url: 192.168.1.187:5240/MAAS
Can't validate endpoint: No MAAS server running at 192.168.1.187:5240/MAAS

Enter the API endpoint url: http://192.168.1.187
Can't validate endpoint: No MAAS server running at http://192.168.1.187

I've done this before, and after 4 attempts I couldn't get Juju to talk to MAAS at a known IP address. Surly *any* of these 4 attempts should be recognized and currently none of them are. From a pure usability standpoint, juju should take several of these inputs and try to contact MAAS. You can easily assume many of these things from the given input.

Even an error message that simply stated the standard default expected MAAS format would have been sufficient to get me through the addition process.

Revision history for this message
Pen Gale (pengale) wrote :

I believe that the default API port is 17070, so 192.168.1.187:17070 should work. With the second and further attempts, you were explicitly telling Juju to call on the wrong port.

I agree that, given a bare IP or domain, Juju should make some guesses about the port, however, or at least include this information in an error message. (The latter is probably safer.)

Changed in juju:
status: New → Confirmed
importance: Undecided → Medium
tags: added: bitesize
Revision history for this message
Pen Gale (pengale) wrote :

Adding bitesize tag, as make a more verbose error message is a straightforward and small solution.

Revision history for this message
Pen Gale (pengale) wrote :

Bleh. Ignore my comments about the port in #1. I was reading the wrong url, and looking at the Juju controller port. I'm obviously not functioning at 100% today :-)

Revision history for this message
Canonical Juju QA Bot (juju-qa-bot) wrote :

This Medium-priority bug has not been updated in 60 days, so we're marking it Low importance. If you believe this is incorrect, please update the importance.

Changed in juju:
importance: Medium → Low
tags: added: expirebugs-bot
Revision history for this message
Jordan Barrett (barrettj12) wrote :

Still present on 2.9-latest when trying to add an Openstack cloud. Any attempt at entering the API endpoint URL fails with no useful error information.

--------------------------------------------------
$ juju add-cloud
This operation can be applied to both a copy on this client and to the one on a controller.
No current controller was detected and there are no registered controllers on this client: either bootstrap one or register one.
Cloud Types
  lxd
  maas
  manual
  openstack
  vsphere

Select cloud type: openstack

Enter a name for your openstack cloud: devstack

Enter the API endpoint url for the cloud []: 172.31.47.119
Can't validate endpoint: No Openstack server running at 172.31.47.119

Enter the API endpoint url for the cloud []: http://172.31.47.119
Can't validate endpoint: No Openstack server running at http://172.31.47.119

Enter the API endpoint url for the cloud []: http://172.31.47.119/identity/v3
Can't validate endpoint: No Openstack server running at http://172.31.47.119/identity/v3

Enter the API endpoint url for the cloud []: 172.31.47.119/identity
Can't validate endpoint: No Openstack server running at 172.31.47.119/identity

Enter the API endpoint url for the cloud []: http://172.31.47.119/identity
Can't validate endpoint: No Openstack server running at http://172.31.47.119/identity

Enter the API endpoint url for the cloud []: ^C
-------------------------------------------------

Changed in juju:
status: Confirmed → Triaged
importance: Low → Medium
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.