3par iSCSI - revert-to-snap of a multi-attach volume leave volume in error state
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
New
|
Undecided
|
Raghavendra Tilay |
Bug Description
Description of problem: While testing revert-to-snapshot of a multi-attached 3par iSCSI backed volume, revert leaves volume in error state.
c-vol report 3par client exception:
2020-06-02 08:51:46.219 39 ERROR cinder.
2020-06-02 08:51:46.219 39 ERROR cinder.
BTW revert to snap of a simple 3par iSCSI volume worked fine.
It also worked fine for an LVM multi-attached volume.
Version-Release number of selected component (if applicable):
python3-
python3-
puppet-
openstack-
python3-
How reproducible:
2 times
Steps to Reproduce:
1. Boot up two instances
2. Create 3par mutli-attached volume
(overcloud) [stack@undercloud-0 ~]$ cinder create 1 --volume-type multiattach --name 3par-ma
+------
| Property | Value |
+------
| attachments | [] |
| availability_zone | nova |
| bootable | false |
| consistencygroup_id | None |
| created_at | 2020-06-
| description | None |
| encrypted | False |
| id | 225bc3df-
| metadata | {} |
| migration_status | None |
| multiattach | True |
| name | 3par-ma |
| os-vol-
| os-vol-
| os-vol-
| os-vol-
| replication_status | None |
| size | 1 |
| snapshot_id | None |
| source_volid | None |
| status | creating |
| updated_at | None |
| user_id | a94a20fdd7534e4
| volume_type | multiattach |
+------
3.
Attach to both instance, write data on volume
(overcloud) [stack@undercloud-0 ~]$ cinder list
+------
| ID | Status | Name | Size | Volume Type | Bootable | Attached to |
+------
| 225bc3df-
+------
4. Create snapshot
(overcloud) [stack@undercloud-0 ~]$ cinder snapshot-create 225bc3df-
+------
| Property | Value |
+------
| created_at | 2020-06-
| description | None |
| id | b999d61d-
| metadata | {} |
| name | spanMA |
| size | 1 |
| status | creating |
| updated_at | None |
| volume_id | 225bc3df-
+------
(overcloud) [stack@undercloud-0 ~]$ cinder snapshot-show b999d61d-
+------
| Property | Value |
+------
| created_at | 2020-06-
| description | None |
| id | b999d61d-
| metadata | {} |
| name | spanMA |
| os-extended-
| os-extended-
| size | 1 |
| status | available |
| updated_at | 2020-06-
| volume_id | 225bc3df-
+------
5. Detach volume from both instances
(overcloud) [stack@undercloud-0 ~]$ nova volume-detach inst1 225bc3df-
(overcloud) [stack@undercloud-0 ~]$ nova volume-detach inst2 225bc3df-
(overcloud) [stack@undercloud-0 ~]$ cinder list
+------
| ID | Status | Name | Size | Volume Type | Bootable | Attached to |
+------
| 225bc3df-
+------
(overcloud) [stack@undercloud-0 ~]$ nova volume-detach inst1 225bc3df-
(overcloud) [stack@undercloud-0 ~]$ cinder list
+------
| ID | Status | Name | Size | Volume Type | Bootable | Attached to |
+------
| 225bc3df-
+------
6. Revert to snapshot:
(overcloud) [stack@undercloud-0 ~]$ cinder --os-volume-
(overcloud) [stack@undercloud-0 ~]$ cinder show 225bc3df-
+------
| Property | Value |
+------
| attached_servers | [] |
| attachment_ids | [] |
| availability_zone | nova |
| bootable | false |
| consistencygroup_id | None |
| created_at | 2020-06-
| description | None |
| encrypted | False |
| id | 225bc3df-
| metadata | |
| migration_status | None |
| multiattach | True |
| name | 3par-ma |
| os-vol-
| os-vol-
| os-vol-
| os-vol-
| replication_status | None |
| size | 1 |
| snapshot_id | None |
| source_volid | None |
| status | error |
| updated_at | 2020-06-
| user_id | a94a20fdd7534e4
| volume_type | multiattach |
+------
Actual results:
Revert fails volume is left in error state.
Expected results:
Revert-to-snap should work leaving volume in available state.
Hi,
We tried to reproduce this using master (Zed). volume. log).
This scenario isn't reproducible; it seems to be fixed.
Attaching cinder output (output.txt) and cinder logs (cinder-
This bug was reported nearly two years ago.
It would be great if you can let us know if this bug is resolved now.
Regards,
Raghavendra Tilay.