Canonical Juju

Conjure-up Kubernetes vpshere

Bug #1846487 reported by Rob Ansems
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Triaged
Low
Unassigned

Bug Description

When deploying Kubernetes by conjure-up on an on-premise vSphere environment, the API endpoint field is not clear. If you fill in the https://fqdn/rest or http://fqdn URL, the error ([Errno -2] Name or service not known) isn't making clear that the field is only asking for the FQDN or ipadres and not for an https or http input.

Revision history for this message
Tim McNamara (tim-clicks) wrote :

Thanks for reporting this.

Did you trip up on this when adding the cloud? (Screenshot attached for the location I think that conjure-up isn't being helpful)

Revision history for this message
Rob Ansems (robansemsvsg) wrote :

Hi Tim,

The screenshot is correct, thank you for attaching it to the bug report.

This error occurs on when creating a new vsphere cloud (see screenshot attached to this post)

Richard Harding (rharding)
Changed in juju:
status: New → Triaged
tags: added: add-cloud usability
Changed in juju:
importance: Undecided → Medium
Revision history for this message
Canonical Juju QA Bot (juju-qa-bot) wrote :

This bug has not been updated in 2 years, 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
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.