VolumeRetypeWithoutMigration fails when cinder-volume is clustered

Bug #1863729 reported by Giulio Fidente on 2020-02-18
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Giulio Fidente

Bug Description

When cinder-volume is clustered, cinder-volume tasks *can* be executed by any node within the same cluser, not only by the node which initially created the volume (setting the os-vol-host-attr:host value accordingly).

The VolumeRetypeWithoutMigration test is assuming the :host value won't change, while it could in case instances were clustered and, in that scenario, cluser_name instead won't change.

Fix proposed to branch: master
Review: https://review.opendev.org/708332

Changed in tempest:
assignee: nobody → Giulio Fidente (gfidente)
status: New → In Progress
description: updated
summary: - VolumeRetype fails when cinder-volume is clustered
+ VolumeRetypeWithoutMigration fails when cinder-volume is clustered
description: updated
Gorka Eguileor (gorka) wrote :

The solution should be simple, just check the cluster_name field and see if it's in a cluster, and if it is ignore the host field and just use the cluster_name, but when I added the cluster functionality for A/A y forgot to add the field to the volume information.

A solution would be to check if Cinder is running microversion 3.7 or higher, and if it is, after we create the volume we ask Cinder for the service information on that volume's host and see if it is in a cluster.

If it is in a cluster we have to compare the cluster for the service running the host value from before and the one from after the retype instead of the host field itself.

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

Other bug subscribers