ERROR listing resources for charm "ch:amd64/kinetic/keystone-572": No revision was found in the Store.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
High
|
Unassigned |
Bug Description
When trying to deploy a charm that has never had support for kinetic (22.10 base), the expectation is that --force allows the deployment to happen
This is the output:
$ juju deploy --series kinetic --channel yoga/edge keystone
ERROR series "kinetic" not supported by charm, supported series are: focal, jammy. Use --force to deploy the charm anyway.
$ juju deploy --force --series kinetic --channel yoga/edge keystone
Located charm "keystone" in charm-hub, revision 572
ERROR listing resources for charm "ch:amd64/
[Test Case]
juju deploy --force --series kinetic --channel yoga/edge keystone
Expected result: keystone charm is deployed on kinetic
Actual result: juju fails to deploy.
Changed in juju: | |
status: | New → Triaged |
importance: | Undecided → High |
The need to be able to succeed with this approach is that it would allow us to enable OpenStack Zed using Ubuntu Kinetic without registering it in the "run-on" stanza in charmcraft.yaml, this is to avoid advertising interim ubuntu releases support in charmhub, and also to allow the different charms to get deployed when not all the patches have been merged yet.