upgrade-charm fails to upgrade local charm
Bug #1606684 reported by
Jay R. Wren
This bug report is a duplicate of:
Bug #1609463: upgrade-charm command is inconsistent with deploy when using local charms.
Edit
Remove
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Triaged
|
High
|
Unassigned | ||
Bug Description
This worked in beta12, but with 2.0-beta13.
$ juju upgrade-charm --path ./anything-charm anything
ERROR cannot upgrade "anything" to "anything-charm"
The metadata.yaml in anything-charm directory defines the charm name as anything, not anything-charm. If the directory name does matter, this should be documented in deploy and upgrade-charm and I'd prefer deploy be consistent with upgrade-charm. I deployed by running:
$ juju deploy ./anything-charm
| Changed in juju-core: | |
| assignee: | nobody → Anastasia (anastasia-macmood) |
| status: | New → Triaged |
| importance: | Undecided → High |
| milestone: | none → 2.0-beta14 |
| assignee: | Anastasia (anastasia-macmood) → nobody |
| Changed in juju-core: | |
| milestone: | 2.0-beta14 → 2.0-beta15 |
| tags: | added: regression |
| Changed in juju-core: | |
| milestone: | 2.0-beta15 → 2.0-beta16 |
| Changed in juju-core: | |
| milestone: | 2.0-beta16 → 2.0-beta17 |
| affects: | juju-core → juju |
| Changed in juju: | |
| milestone: | 2.0-beta17 → none |
| milestone: | none → 2.0-beta17 |
| Changed in juju: | |
| milestone: | 2.0-beta17 → 2.0-beta18 |
| Changed in juju: | |
| milestone: | 2.0-beta18 → 2.0-beta19 |
| Changed in juju: | |
| milestone: | 2.0-beta19 → 2.0-rc1 |
| Changed in juju: | |
| milestone: | 2.0-rc1 → 2.0-rc2 |
| Changed in juju: | |
| milestone: | 2.0-rc2 → 2.0.0 |
| Changed in juju: | |
| milestone: | 2.0-rc3 → 2.0.0 |
To post a comment you must log in.
