Comment 19 for bug 1951182

For the record, with Juju 3.2-beta1, I have the same issue. An export-bundle produces various entries along these lines:

  cinder:
    charm: cinder
    channel: zed/stable
    revision: 594
    resources:
      policyd-override: 0
    num_units: 3
    to:
    - lxd:0
    - lxd:1
    - lxd:2
    options:
      block-device: None
      glance-api-version: 2
      openstack-origin: cloud:jammy-zed
      vip: [REDACTED]
    constraints: arch=amd64
    storage:
      block-devices: loop,10240M

I have to remove all the 'storage' and 'resources' sections to get a bundle I can then deploy.

Example errors whilst trying to deploy exported bundle:

- deploy application ceph-mon from charm-hub on jammy with quincy/stable
ERROR cannot deploy bundle: while adding pending resource info for "alert-rules": bad resource metadata: bad info: bad metadata: resource missing filename

ERROR cannot deploy bundle: cannot add unit for application "cinder": acquiring machine to host unit "cinder/0": cannot assign unit "cinder/0" to machine 0/lxd/2: adding storage to lxd container not supported (not supported)