upgrade-charm --switch plus --channel can lead to wrong charm series
Bug #1993758 reported by
Haw Loeung
This bug report is a duplicate of:
Bug #1990182: refresh: ERROR selecting releases: unknown series for version: "22.10".
Edit
Remove
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
High
|
Unassigned |
Bug Description
Hi,
Per Mattermost, we recently published new per-series charms to charmhub under a shorter name. On switching with `juju upgrade-charm --switch new-charm-name --channel edge`, the wrong series is selected. A following upgrade-charm does the right thing.
See https:/
Changed in juju: | |
milestone: | none → 3.0.1 |
importance: | Undecided → High |
status: | New → Triaged |
Changed in juju: | |
milestone: | 3.0.1 → none |
To post a comment you must log in.
Today the metadata.yaml and the manifest.yaml for cs:~ubuntu- repository- cache-charmers/ ubuntu- repository- cache-59 do not match. Juju is using the manifest, so I'm having to force deploy the charm.
What version of juju is the now running in the model? And what version of juju was running in the model when cs:~ubuntu- repository- cache-charmers/ ubuntu- repository- cache-59 was deployed?
What version of cs:~ubuntu- repository- cache-charmers/ ubuntu- repository- cache was originaly deployed? In this situation history from the beginning could impact the outcome unfortunately.