Running upgrade-charm directly after deploy prevents new deploys with LXD Profile data
Bug #1808515 reported by
Simon Richardson
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Invalid
|
High
|
Unassigned |
Bug Description
Running upgrade-charm directly after deploying the charm, which has a LXD profile breaks the potential to upgrade-charm in the future.
The uniter doesn't seem to clean up the instanceCharmPr
The work around is to remove the document inside the instanceCharmPr
Changed in juju: | |
milestone: | none → 2.5.1 |
Changed in juju: | |
assignee: | nobody → Richard Harding (rharding) |
Changed in juju: | |
milestone: | 2.5.1 → 2.5.2 |
assignee: | Richard Harding (rharding) → nobody |
Changed in juju: | |
milestone: | 2.5.2 → 2.5.3 |
Changed in juju: | |
milestone: | 2.5.3 → 2.5.4 |
Changed in juju: | |
milestone: | 2.5.4 → 2.5.5 |
Changed in juju: | |
milestone: | 2.5.6 → 2.5.8 |
Changed in juju: | |
status: | Triaged → Invalid |
To post a comment you must log in.