Comment 1 for bug 1768845

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:
>
> 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://bugs.launchpad.net/bugs/1768845
>
> Title:
> add-k8s incorrectly reports "cloud already exists"
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1768845/+subscriptions
>