Cinder-backed images occasionally fail to clone in A-A

Bug #1906286 reported by Mohammed Naser
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Cinder
Triaged
Medium
Unassigned

Bug Description

When using Cinder-backed images inside Glance in combination with Active-Active, it leads to a situation where the original image would fallback to the download image flow which can be very taxing on environments.

The root cause of this is that Cinder tries to find for any matching volumes that _only_ match on the host the volume is being launched on, which makes sense in a non clustered Cinder environment, but does not make sense in an environment where the base volume can potentially be accessible in the cluster, but on a differnet host.

The code in question is the following:

https://github.com/openstack/cinder/blob/075ab6c85f6d6a069e96f175a1f4950eeedfbcbb/cinder/volume/flows/manager/create_volume.py#L680-L681

Changed in cinder:
status: New → Triaged
importance: Undecided → Medium
tags: added: active-active backup glance
Revision history for this message
Rajat Dhasmana (whoami-rajat) wrote :

This should be fixed with the patch[1]
I found the same issue while testing multiple glance cinder stores with different backend configuration, see my comment on the review for the that scenario.

[1] https://review.opendev.org/c/openstack/cinder/+/755654

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.