ScaleIO: Volume name not set correctly in ScaleIO after re-typing of attached volume

Bug #1709705 reported by Martin Chlumsky
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Cinder
Confirmed
Undecided
tssgery

Bug Description

Some background info: we map volume types to ScaleIO clusters so when we re-type a volume it leads to the volume being migrated between different SIO clusters.

When we re-type an attached volume, the name of the volume in SIO does not get set correctly.

The name of volume that does get set is the encoded uuid of the intermediate volume that becomes the final volume.

I think I narrowed it down to this line:
https://github.com/openstack/cinder/blob/dd3742f6069087ba981f97d220b5cfcf314f7bb9/cinder/volume/drivers/dell_emc/scaleio/driver.py#L1115

It seems only 'available' volumes get the name set correctly.

Tags: driver
tssgery (eric-aceshome)
Changed in cinder:
assignee: nobody → tssgery (eric-aceshome)
summary: - Volume name not set correctly in ScaleIO after re-typing of attached
- volume
+ ScaleIO: Volume name not set correctly in ScaleIO after re-typing of
+ attached volume
Changed in cinder:
status: New → Confirmed
Revision history for this message
tssgery (eric-aceshome) wrote :

I will need to investigate any side effects with renaming the original volume which is attached/in-use

Revision history for this message
Martin Chlumsky (martin-chlumsky) wrote :

To help with prioritizing this, I don't know that this actually breaks anything in OpenStack.

I only noticed because it "broke" one of my scripts that uses the volume UUIDs in OpenStack and re-conciles them against the volume names in ScaleIO.

I really don't know how/if the volume names are used.

Revision history for this message
tssgery (eric-aceshome) wrote :

I am not sure if anything breaks either, but I'd like to validate it.

Can you please attach your volume types and extra-specs here so I can duplicate exactly what you see?

Revision history for this message
Martin Chlumsky (martin-chlumsky) wrote :

Here you go:

+--------------------+--------------------------------------------------------------------------------------------------+
| Field | Value |
+--------------------+--------------------------------------------------------------------------------------------------+
| access_project_ids | None |
| description | None |
| id | xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx |
| is_public | True |
| name | ssd1-zone1 |
| properties | provisioning:type='thick', sio:provisioning_type='thick', volume_backend_name='scaleio_cluster1' |
+--------------------+--------------------------------------------------------------------------------------------------+

+--------------------+--------------------------------------------------------------------------------------------------+
| Field | Value |
+--------------------+--------------------------------------------------------------------------------------------------+
| access_project_ids | None |
| description | None |
| id | xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx |
| is_public | True |
| name | ssd1-zone2 |
| properties | provisioning:type='thick', sio:provisioning_type='thick', volume_backend_name='scaleio_cluster2' |
+--------------------+--------------------------------------------------------------------------------------------------+

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.