[2.8.5] Juju destroy kubernetes model hangs on "destroying" forever

Bug #1901439 reported by Pedro Guimarães
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Canonical Juju
Fix Released
High
Yang Kelvin Liu

Bug Description

Hi,

Using Juju 2.8.5. I've destroyed my Charmed Kubernetes cluster before destroying the model deployed on top of kubernetes itself.

Once I've realized that, I've ran "juju destroy-model kubeflow --force", still it hanged on "destroying" status and none of the counts (applications, units, etc) were decreasing.

Tags: k8s
Revision history for this message
Pedro Guimarães (pguimaraes) wrote :

I am aware of a similar bug: https://bugs.launchpad.net/juju/+bug/1885029
However, in this case, I did destroy the k8s cluster before.

Pen Gale (pengale)
tags: added: k8s
Changed in juju:
importance: Undecided → High
status: New → Triaged
assignee: nobody → Yang Kelvin Liu (kelvin.liu)
milestone: none → 2.8.7
Changed in juju:
status: Triaged → In Progress
Revision history for this message
Yang Kelvin Liu (kelvin.liu) wrote :

This is a generic issue of `--force` for both IaaS and CaaS.

https://github.com/juju/juju/pull/12200 will be landed to 2.8 to fix this issue.

Revision history for this message
Pen Gale (pengale) wrote :

I just marked https://bugs.launchpad.net/juju/+bug/1885029 as a duplicate of this. There is potentially more troubleshooting info in that bug.

Changed in juju:
status: In Progress → Fix Committed
Changed in juju:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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