Comment 7 for bug 2049574

One more observation, when I create an instances from image, libvirt shows this message.

2024-01-19 06:45:06.536 7 INFO nova.virt.block_device [req-da372940-2784-4aba-881f-7636460efb46 req-bffdffd6-7521-4450-9ab9-93bac32789e1 a828b4ad4d794e18ac9c6238e893522d 1f4d24639d564e40816d90be4cac8ecd - - default default] [instance: 330922ac-8333-4ee7-a634-0075a00f1fd7] Booting with volume-backed-image 0e1aa7ba-23cc-4ced-8aa2-c9f78535d435 at /dev/vda

But none of the volumes are with this ID.

openstack server show results provides the correct volume ID. But why does this mismatch in the first place?

attached_volumes:
- attachment_id: null
  bdm_id: null
  delete_on_termination: false
  device: null
  id: c22d487d-ab7a-4373-b69f-91cd02f32cc8

When creating Volume based instances, the Vol ID from nova log during creation and the actual image id is the same.

Could this be the problem?