document charm upgrade conflict resolution
Bug #1195277 reported by
William Reade
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | ||
|---|---|---|---|---|---|---|
| juju-core | ||||||
| Docs |
Triaged
|
Medium
|
Unassigned | |||
Bug Description
We haven't communicated the expected process for resolving charm upgrade conflicts. It is:
* juju ssh $UNIT # and resolve conflicts manually with git
* juju resolved $UNIT # and you're done
...but if nobody knows about it they're not helped.
Revision history for this message
| William Reade (fwereade) wrote | #1 |
| Changed in juju-core: | |
| assignee: | nobody → Nick Veitch (evilnick) |
| tags: |
added: docs removed: doc |
| Changed in juju-core: | |
| assignee: | Nick Veitch (evilnick) → nobody |
| no longer affects: | juju-core |
To post a comment you must log in.
We should also make clear the sorts of changes it's reasonable to make to a charm, and that the charmer is responsible for the contents of the directory as it runs, and for taking potential upgrade collisions into account.