juju refresh --switch ./local fails for metadata v1 charm
Bug #1925670 reported by
John A Meinel
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
High
|
Simon Richardson |
Bug Description
I'm testing some things out, and I published a charm to charmhub. I then went to try to switch to the local version of the charm. It is currently using metadata v1, only I edit the .charm file to remove manifest.yaml because of our series vs metadata.yaml bug.
$ juju upgrade-charm jam-k8s-api-test --switch ./jam-k8s-
Looking up metadata for charm-hub charm "jam-k8s-api-test" from channel stable
ERROR series "focal" not supported by charm, supported series are: kubernetes
summary: |
- juju upgrade-charm --switch ./local fails for metadata v1 charm + juju refresh --switch ./local fails for metadata v1 charm |
Changed in juju: | |
milestone: | 2.9.1 → 2.9.2 |
Changed in juju: | |
milestone: | 2.9.2 → 2.9.3 |
Changed in juju: | |
milestone: | 2.9.3 → 2.9.4 |
Changed in juju: | |
status: | Incomplete → Triaged |
Changed in juju: | |
milestone: | 2.9.4 → 2.9.5 |
summary: |
- juju refresh --switch ./local fails for metadata v1 charm + juju refresh --switch ./local fails for metadata v2 charm |
summary: |
- juju refresh --switch ./local fails for metadata v2 charm + juju refresh --switch ./local fails for metadata v1 charm |
Changed in juju: | |
milestone: | 2.9.5 → 2.9.6 |
Changed in juju: | |
milestone: | 2.9.6 → 2.9.7 |
Changed in juju: | |
assignee: | nobody → Simon Richardson (simonrichardson) |
Changed in juju: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
if this was prior to landing the change to assume series means V1 metadata (https:/ /github. com/juju/ juju/pull/ 12915) then we probably reasoned about the charm as V2 when it was in the store, then V1 when manifest.yaml was deleted locally.
It raises the question though, whether changing metadata format version *downward* should be supported.