Canonical Juju

Running upgrade-charm directly after deploy prevents new deploys with LXD Profile data

Bug #1808515 reported by Simon Richardson on 2018-12-14

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	Canonical Juju	Invalid	High	Unassigned	Canonical Juju 2.5.8

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 instanceCharmProfileData document when the deployment finishes. Once the original deploy has past a certain point (unsure exactly what that point is yet), upgrades can be applied over and over.

The work around is to remove the document inside the instanceCharmProfileData that corresponds to the machine.

Simon Richardson (simonrichardson) on 2018-12-14

Changed in juju:
milestone:	none → 2.5.1

Ian Booth (wallyworld) on 2019-01-28

Changed in juju:
assignee:	nobody → Richard Harding (rharding)

Richard Harding (rharding) on 2019-01-29

Changed in juju:
milestone:	2.5.1 → 2.5.2
assignee:	Richard Harding (rharding) → nobody

Canonical Juju QA Bot (juju-qa-bot) on 2019-03-11

Changed in juju:
milestone:	2.5.2 → 2.5.3

Canonical Juju QA Bot (juju-qa-bot) on 2019-03-26

Changed in juju:
milestone:	2.5.3 → 2.5.4

Canonical Juju QA Bot (juju-qa-bot) on 2019-04-02

Changed in juju:
milestone:	2.5.4 → 2.5.5

Anastasia (anastasia-macmood) on 2019-05-14

Changed in juju:
milestone:	2.5.6 → 2.5.8

Simon Richardson (simonrichardson) on 2019-05-21

Changed in juju:
status:	Triaged → Invalid

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

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