Comment 3 for bug 1991511

The workflow is something like:
1) build a charm, revision 1 that uses a sidecar resource at revision 3
2) new version of the charm, revision 5, no longer has a resource
3) Try to deploy the old version of the charm `juju deploy charm --revision
1` fails because the track of the charm (latest) no longer has a resource
for 'sidecar', but you can force it with `juju deploy charm --revision 1
--resource sidecar=3`

But ultimately that is a workaround. We probably need to work with Charmhub
for them to expose the information about known revisions of resources
associated with an old revision of a charm.

On Thu, Oct 13, 2022 at 8:35 AM Joseph Phillips <email address hidden>
wrote:

> I'm a little unclear on the steps here.
>
> "the next stage of testing is to deploy the old version of the charm
> (that includes the workload) and then test a charm upgrade to the new
> version that doesn't include the workload."
>
> Are you deploying the same charm into the model with a different
> application name here?
>
> What is the mode of "upgrade".
>
> ** Changed in: juju
> Status: Triaged => Incomplete
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: juju bugs
> https://bugs.launchpad.net/bugs/1991511
>
> Title:
> Unable to deploy charm of older revision from channel where an image
> resource has been removed in newer version
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1991511/+subscriptions
>
>