This bug was initially created as a copy of Bug #2037034 When creating an attachment with the new attachments API, it requires a instance_uuid as a mandatory field which is not available when we create an attachment from glance cinder store failing the image create operation.
Verified on: openstack-cinder-15.4.0-1.20220114193342.58f0e73.el8ost.noarch On a deployment with Glance over Cinder over netapp iSCSI Lets upload an image to Glance: (overcloud) [stack@undercloud-0 ~]$ glance image-create --disk-format qcow2 --container-format bare --file rhel-8.5-update-2-x86_64-kvm.qcow2 --name rhel8.5 --progress [=============================>] 100% +------------------+----------------------------------------------------------------------------------+ | Property | Value | +------------------+----------------------------------------------------------------------------------+ | checksum | 6e494d2b830cd2f2372364b035e93598 | | container_format | bare | | created_at | 2022-03-02T10:42:45Z | | direct_url | cinder://d2594f15-3f72-468b-a9a0-dce6a69a930e | | disk_format | qcow2 | | id | 0d5a60dd-f44b-4bb7-9408-804af7eb6f1f | | min_disk | 0 | | min_ram | 0 | | name | rhel8.5 | | os_hash_algo | sha512 | | os_hash_value | 5bda0e42020f8d8e3d547de633e69c5ff442aa0b59d92e81d5bb6142fc95f4678049f72264689077 | | | 26c66d42f8498730f5ec5add9cb7f52dfe1f716410b78fa2 | | os_hidden | False | | owner | 19d5920d1789476d9c3541e3da5574aa | | protected | False | | size | 779681792 | | status | active | | stores | default_backend | | tags | [] | | updated_at | 2022-03-02T10:43:04Z | | virtual_size | Not available | | visibility | shared | +------------------+----------------------------------------------------------------------------------+ Successfully upload an image to Glance over Cinder. When creating an attachment with the new attachments API, it now requires a optional, rather than a previously mandatory, instance_uuid field. Instance_uuid field is not available when we create an attachment from glance cinder store, which is why image creation would fail before but with this fix/optional field status, the operation completes fine, good to verify.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Red Hat OpenStack Platform 16.1.8 bug fix and enhancement advisory), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2022:0986