Migrating an attached volume to other AZ leaves original volume intact.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
New
|
Undecided
|
Unassigned |
Bug Description
Description of problem:
Version-Release number of selected component (if applicable):
puppet-
python2-
openstack-
python2-
python-
How reproducible:
Unsure
Steps to Reproduce:
1. Boot an instance (AZ=nova)
2. Create a triple0 (lvm AZ=nova) volume
cinder create 1 --volume-type tripleo --availability-zone nova --name vol-lvm2
+------
| Property | Value |
+------
| attachments | [] |
| availability_zone | nova |
| bootable | false |
| consistencygroup_id | None |
| created_at | 2018-11-
| description | None |
| encrypted | False |
| id | 23ecbc2a-
| metadata | {} |
| migration_status | None |
| multiattach | False |
| name | vol-lvm2 |
| os-vol-
| os-vol-
| os-vol-
| os-vol-
| replication_status | None |
| size | 1 |
| snapshot_id | None |
| source_volid | None |
| status | available |
| updated_at | 2018-11-
| user_id | 1015400afd2f4c4
| volume_type | tripleo |
+------
3. Attach vol to instance
nova volume-attach 2d300b8d-
+------
| Property | Value |
+------
| device | /dev/vdb |
| id | 23ecbc2a-
| serverId | 2d300b8d-
| volumeId | 23ecbc2a-
+------
Vol get's attached:
| 23ecbc2a-
4. Migrate to nfs (otherAZ)
cinder migrate 23ecbc2a-
Request to migrate volume 23ecbc2a-
5. Migration works, new nfs vol is in use, but source vol remains available.
cinder list
+------
| ID | Status | Name | Size | Volume Type | Bootable | Attached to |
+------
| 23ecbc2a-
| 73ed2a59-
Details of volumes:
Source tripl0 lvm vol:
cinder show 23ecbc2a-
+------
| Property | Value |
+------
| attached_servers | [] |
| attachment_ids | [] |
| availability_zone | nova |
| bootable | false |
| consistencygroup_id | None |
| created_at | 2018-11-
| description | None |
| encrypted | False |
| id | 23ecbc2a-
| metadata | |
| migration_status | migrating |
| multiattach | False |
| name | vol-lvm2 |
| os-vol-
| os-vol-
| os-vol-
| os-vol-
| replication_status | None |
| size | 1 |
| snapshot_id | None |
| source_volid | None |
| status | available |
| updated_at | 2018-11-
| user_id | 1015400afd2f4c4
| volume_type | tripleo |
+------
Target nfs volume
cinder show 73ed2a59-
+------
| Property | Value |
+------
| attached_servers | ['2d300b8d-
| attachment_ids | ['f1eaed7a-
| availability_zone | dc2 |
| bootable | false |
| consistencygroup_id | None |
| created_at | 2018-11-
| description | None |
| encrypted | False |
| id | 73ed2a59-
| metadata | |
| migration_status | target:
| multiattach | False |
| name | vol-lvm2 |
| os-vol-
| os-vol-
| os-vol-
| os-vol-
| replication_status | None |
| size | 1 |
| snapshot_id | None |
| source_volid | None |
| status | in-use |
| updated_at | 2018-11-
| user_id | 1015400afd2f4c4
| volume_type | tripleo |
+------
Actual results:
Volume is migrated\attached, but original volume remains available.
If I do migrate an unattached volume, source volume gets deleted as expected.
Expected results:
Expect source volume to get deleted, as happens with migrate of a none attached volume.
Additional info:
Not sure this might be an OS-brick issue.
Another tip notice triple0 (lvm) backend's volume_
This is Nova bug 1803961