add-k8s incorrectly reports "cloud already exists"
Bug #1768845 reported by
Cory Johns
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
High
|
Ian Booth |
Bug Description
Steps to reproduce:
$ juju add-k8s kubernetes
$ juju remove-cloud kubernetes
Removed details of personal cloud "kubernetes"
$ juju show-cloud kubernetes
ERROR cloud "kubernetes" not found
$ juju add-k8s kubernetes
ERROR cloud "kubernetes" already exists (already exists)
Note that the cluster information is updated, but it is also updated if you don't remove-cloud first. Perhaps add-k8s should support an --overwrite option?
Changed in juju: | |
status: | New → Triaged |
importance: | Undecided → High |
tags: | added: add-cloud add-k8s caas k8s remove-cloud |
Changed in juju: | |
milestone: | none → 2.4-beta2 |
assignee: | nobody → Yang Kelvin Liu (kelvin.liu) |
Changed in juju: | |
assignee: | Yang Kelvin Liu (kelvin.liu) → Christopher Lee (veebers) |
Changed in juju: | |
milestone: | 2.4-beta2 → none |
Changed in juju: | |
milestone: | none → 2.4-rc1 |
Changed in juju: | |
assignee: | Christopher Lee (veebers) → Ian Booth (wallyworld) |
Changed in juju: | |
status: | Triaged → In Progress |
Changed in juju: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
It sounds more like we are leaving some bit of information behind that we
then treat incorrectly. We probably just need to be more careful around
'remove-cloud' really deleting it.
On Thu, May 3, 2018 at 3:31 PM, Cory Johns <email address hidden> wrote:
> Public bug reported: /bugs.launchpad .net/bugs/ 1768845 /bugs.launchpad .net/juju/ +bug/1768845/ +subscriptions
>
> Steps to reproduce:
>
> $ juju add-k8s kubernetes
> $ juju remove-cloud kubernetes
> Removed details of personal cloud "kubernetes"
> $ juju show-cloud kubernetes
> ERROR cloud "kubernetes" not found
> $ juju add-k8s kubernetes
>
>
> ERROR cloud "kubernetes" already exists (already exists)
>
> Note that the cluster information is updated, but it is also updated if
> you don't remove-cloud first. Perhaps add-k8s should support an
> --overwrite option?
>
> ** Affects: juju
> Importance: Undecided
> Status: New
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: juju bugs
> https:/
>
> Title:
> add-k8s incorrectly reports "cloud already exists"
>
> To manage notifications about this bug go to:
> https:/
>