Umanaged volumes missing from Cinder manageable-list when using 3par FC/iscsi
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Fix Released
|
Wishlist
|
Unassigned |
Bug Description
Description of problem: Umnaged Cinder volumes don't show up on manageable-list, when testing with 3par FC/iSCSI backend, on LVM iSCSI this works fine.
Version-Release number of selected component (if applicable):
python-
python-
openstack-
How reproducible:
Every time
Steps to Reproduce:
1. Configure a system with 3par FC or iSCSI backend
cinder service-list
| cinder-volume | hostgroup@3parfc | nova | enabled | up | 2019-03-
The backend config section:
[3parfc]
volume_backend_name = 3parfc
hpe3par_api_url = https:/
hpe3par_username = admin
hpe3par_password = .......
hpe3par_cpg = SSD_r5
san_ip = .......
san_login = admin
san_password = ......
volume_driver = cinder.
hpe3par_debug = true
hpe3par_
hpe3par_
max_over_
reserved_percentage = 15
use_multipath_
image_volume_
2. Create a Cinder volume
cinder create 1 --name vol1
+------
| Property | Value |
+------
| attachments | [] |
| availability_zone | nova |
| bootable | false |
| consistencygroup_id | None |
| created_at | 2019-03-
| description | None |
| encrypted | False |
| id | bb75366c-
| metadata | {} |
| migration_status | None |
| multiattach | False |
| name | vol1 |
| os-vol-
| os-vol-
| os-vol-
| os-vol-
| replication_status | disabled |
| size | 1 |
| snapshot_id | None |
| source_volid | None |
| status | creating |
| updated_at | None |
| user_id | 65a72bf00f3e4f9
| volume_type | None |
+------
cinder show bb75366c-
+------
| Property | Value |
+------
| attachments | [] |
| availability_zone | nova |
| bootable | false |
| consistencygroup_id | None |
| created_at | 2019-03-
| description | None |
| encrypted | False |
| id | bb75366c-
| metadata | {} |
| migration_status | None |
| multiattach | False |
| name | vol1 |
| os-vol-
| os-vol-
| os-vol-
| os-vol-
| replication_status | disabled |
| size | 1 |
| snapshot_id | None |
| source_volid | None |
| status | available |
| updated_at | 2019-03-
| user_id | 65a72bf00f3e4f9
| volume_type | None |
+------
3. Even before I unmanage the ^volume, we hit an issue as I should have already seen several volumes here already, from previous umanange attempts and other systems which share this backend.
cinder manageable-list hostgroup@
+------
| reference | size | safe_to_manage | reason_not_safe | cinder_id | extra_info |
+------
+------
4. Now I'll unmanage the volume we created on step 2
cinder unmanage bb75366c-
5. Recheck manageable-list, again empty.
We should have at least gotten the volume we unmanged on step 3.
cinder manageable-list hostgroup@
+------
| reference | size | safe_to_manage | reason_not_safe | cinder_id | extra_info |
+------
+------
Actual results:
Manageable list returns no volumes which we can import.
Expected results:
I should get a list of unmanaged volumes on the backend that I can import/manage.
Tested this on another system same version but with LVM iSCSI and it worked fine, the unmanaged volume would shouldup on the managelable list.
Additional info: Unsure if it's either a config or 3par specific bug.
https:/
supported operation include:
Manage and unmanage a volume.
Manage and unmanage a snapshot.
3par hasn't implemented get_manageable_ volumes( ) yet.