running `juju remove-unit` on microk8s backed model prints stacktrace
Bug #1928192 reported by
Martin Kalcok
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Fix Released
|
High
|
Ian Booth | ||
Bug Description
When I run command `juju remove-unit` without any arguments on model that is backed by microk8s I get following stacktrace:
https:/
I'm not sure if the fact that it's a microk8s cloud matters because I don't have other clouds on my machine. But when I run the same command on other machine that has OpenStack based cloud I get only expected error message, no panic/stacktrace.
juju version: 2.9.0-ubuntu-amd64
Installation method: snap
| Changed in juju: | |
| milestone: | none → 2.9.1 |
| importance: | Undecided → High |
| status: | New → Triaged |
| tags: | added: bitesize k8s |
| Changed in juju: | |
| milestone: | 2.9.1 → 2.9.2 |
| Changed in juju: | |
| assignee: | nobody → Ian Booth (wallyworld) |
| status: | Triaged → In Progress |
| Changed in juju: | |
| status: | In Progress → Fix Committed |
| Changed in juju: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
