This is not backend related, generally when we create a bootable volume from image, in case of an error, we don't clean up the image metadata entry in DB. Incase of creating instance from bootable volume, during first failure, nova reschedules instance creation and we see the above trace during second attempt due to a residue glance image metadata entry in DB.
Hi Sofia,
This is not backend related, generally when we create a bootable volume from image, in case of an error, we don't clean up the image metadata entry in DB. Incase of creating instance from bootable volume, during first failure, nova reschedules instance creation and we see the above trace during second attempt due to a residue glance image metadata entry in DB.