lxd profile remains after model is removed
Bug #1968529 reported by
Robert Gildein
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Triaged
|
Low
|
Unassigned | ||
Bug Description
While deploying charmed-kubernetes (requires a custom lxd profile) on my
local lxd, I found out I had 266 lxd profiles [1].
```bash
$ lxc profile list --format csv | wc -l
267
```
Some of these profiles are from manually created models, but a large part
comes from integration tests that have been run by `pytest-operator`
and `zaza`.
In my opinion, the profiles should not be left after the model was removed.
| description: | updated |
| Changed in juju: | |
| status: | New → Triaged |
| importance: | Undecided → Low |
Revision history for this message
| Heather Lanigan (hmlanigan) wrote | #1 |
Revision history for this message
| Robert Gildein (rgildein) wrote | #2 |
To post a comment you must log in.
During implementation, there was a decision made to not delete lxd profiles created by juju. This applies to profiles supplied by charms. The same behavior as for juju in general, and for each model.