destroying a controller and then trying to recreate it tells me it already exists

[Tom Haddon]

I created a juju k8s controller on microk8s, and then wanted to destroy it and recreate it. However, it tells me after destroying it that a controller with the same name already exists on the cluster.

https://paste.ubuntu.com/p/rn6cctvdQB/

[John A Meinel (jameinel)]

There is a controller-micro namespace running with a modeloperator and
controller-0. Is the issue that it didn't cleanup properly?
You should be able to 'kubectl delete namespace controller-micro'

However, you shouldn't need to do so .

On Tue, Dec 15, 2020 at 6:15 AM Tom Haddon <email address hidden>
wrote:

> Public bug reported:
>
> I created a juju k8s controller on microk8s, and then wanted to destroy
> it and recreate it. However, it tells me after destroying it that a
> controller with the same name already exists on the cluster.
>
> https://paste.ubuntu.com/p/rn6cctvdQB/
>
> ** 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/1908258
>
> Title:
> destroying a controller and then trying to recreate it tells me it
> already exists
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1908258/+subscriptions
>

[Tom Haddon (mthaddon)]

I believe that's the issue, yes (that it didn't clean up properly). Obviously I can work around it by manually deleting the namespace in kubernetes, but wanted to report this bug and ask if there's any info I can provide that'd help identify why this happened.

[Ian Booth (wallyworld)]

I am fairly sure that destroy-model will cleanup the model's namespace so the bug appears specific to destroy-controller. FWIW kill-controller does clean up the namespace (but we prefer people use destroy-controller).

[Launchpad Janitor (janitor)]

[Expired for Canonical Juju because there has been no activity for 60 days.]