tempest

VolumeRetypeWithoutMigration fails when cinder-volume is clustered

Bug #1863729 reported by Giulio Fidente
14
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tempest
Confirmed
Undecided
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.

See original description
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to tempest (master)

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

Changed in tempest:
assignee: nobody → Giulio Fidente (gfidente)
status: New → In Progress
Giulio Fidente (gfidente)
description: updated
summary: - VolumeRetype fails when cinder-volume is clustered
+ VolumeRetypeWithoutMigration fails when cinder-volume is clustered
description: updated
Revision history for this message
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.

Revision history for this message
Martin Kopec (mkopec) wrote :

What is the status here? The related review is -w by its owner. Is anyone working on this?

Revision history for this message
Giulio Fidente (gfidente) wrote :

Martin, I think the necessary "cluster_name" property of a volume wasn't exposed in previous versions of the API, but it might be now and we might able to reprise the existing submission then.

Gorka, can you help us understand if https://review.opendev.org/#/c/708332/1/tempest/api/volume/admin/test_volume_retype.py is supposed to work with recent stable branches?

Revision history for this message
Martin Kopec (mkopec) wrote :

how is it looking now? anything I can help with?

Revision history for this message
Giulio Fidente (gfidente) wrote :

hi Martin, thanks for jumping in... help would be much appreciated here indeed.

I think the best way forward is what Gorka suggested here https://bugs.launchpad.net/tempest/+bug/1863729/comments/2 but I couldn't find myself the time to work on it

Gorka is the cluster_name property exposed in recent microversions?

Revision history for this message
Lukas Piwowarski (lukas-piwowarski) wrote :

Hi, it looks like nobody is working on this. I'm moving this back to confirmed as the test is still not fixed [1].

[1] https://github.com/openstack/tempest/blame/master/tempest/api/volume/admin/test_volume_retype.py

Changed in tempest:
status: In Progress → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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