In the first case Cinder gets request about a specific snapshot straight away. Not sure where this data comes from, maybe Horizon requests meta from Glance first and finds block_device_mapping meta. Then in the end we can see that Cinder gets a POST request with this snapshot id, and creates a volume from this snapshot, does not touch the image at all (seems so).
In the second case Cinder gets a lot of requests, some for snapshots (but no specific one), and in the end we see a POST request to Cinder without the snapshot id, which causes Cinder to create a new volume not from snapshot but from image, and fail.
Looks like it's indeed an issue in Horizon (or Glance?). paste.openstack .org/show/ 626882/ paste.openstack .org/show/ 626881/
Here is how requests to Cinder API look like:
- VM is spawn from image with Create a new Volume: http://
- Create Volume is used on Images tab: - http://
In the first case Cinder gets request about a specific snapshot straight away. Not sure where this data comes from, maybe Horizon requests meta from Glance first and finds block_device_ mapping meta. Then in the end we can see that Cinder gets a POST request with this snapshot id, and creates a volume from this snapshot, does not touch the image at all (seems so).
In the second case Cinder gets a lot of requests, some for snapshots (but no specific one), and in the end we see a POST request to Cinder without the snapshot id, which causes Cinder to create a new volume not from snapshot but from image, and fail.