k8s cloud name can't start with a number

Bug #1861325 reported by Adam Israel
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Triaged
Low
Unassigned

Bug Description

Juju version: 2.7.1-disco-amd64

If I try to bootstrap a k8s cloud that begins with a number, it fails saying the credential name is not valid.

Steps to reproduce:

$ microk8s.config|juju add-k8s 1234-5678-2345-k8s --client
k8s substrate "microk8s/localhost" added as cloud "1234-5678-2345-k8s".
You can now bootstrap to this cloud by running 'juju bootstrap 1234-5678-2345-k8s'.

$ juju bootstrap 1234-5678-2345-k8s
ERROR credential name "1234-5678-2345-k8s" not valid

If I append an alphabetical character to the cloud name, the bootstrap will succeed.

Revision history for this message
Richard Harding (rharding) wrote :

Yes, this is a requirement in the Juju names standards where we don't allow things to start with a number as it messes up meaningful sorting and such.

The messaging should be more clear about what the name error is though.

Changed in juju:
status: New → Triaged
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.

Other bug subscribers

Remote bug watches

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