volume stuck in deleting when "host" has been changed

Bug #1588148 reported by Wenjun Wang
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Cinder
New
Undecided
Unassigned

Bug Description

The volume info before I change the "host" in /etc/cinder/cinder.conf.

[root@localhost ~]# cinder show vol1
+--------------------------------+---------------------------------------------------------------------+
| Property | Value |
+--------------------------------+---------------------------------------------------------------------+
| attachments | [] |
| availability_zone | nova |
| bootable | false |
| consistencygroup_id | None |
| created_at | 2016-06-02T11:25:13.000000 |
| description | None |
| encrypted | False |
| id | e831ff01-f334-4eb7-8497-0fbed8667087 |
| metadata | {'volname': 'OpenCos_6354186906535030841', 'poolname': 'ipPOOL_02'} |
| migration_status | None |
| multiattach | False |
| name | vol1 |
| os-vol-host-attr:host | localhost.localdomain@KS3200ISCSIDriver#ipPOOL_02 |
| os-vol-mig-status-attr:migstat | None |
| os-vol-mig-status-attr:name_id | None |
| os-vol-tenant-attr:tenant_id | 97330b92c2144c0ea9b8826038d3abe3 |
| replication_status | disabled |
| size | 1 |
| snapshot_id | None |
| source_volid | None |
| status | available |
| updated_at | 2016-06-02T11:25:15.000000 |
| user_id | 346ce385360c43588f48349ed8f4159e |
| volume_type | ks3200 |
+--------------------------------+---------------------------------------------------------------------+

Then I changed the "host" to "cinder", and the vol1 cound not delete, it will be stuck in deleting.

I have the following ideas:
* if we can change the "host", it's better to provide a API to handle this, and "host" change will not make influence on volume usages.
* if we don't want anybody to change the "host", then don't make it apper in conf, generate it automaticlly.

Wenjun Wang (wangwenjun)
Changed in cinder:
assignee: nobody → Wenjun Wang (wangwenjun)
Revision history for this message
Sean McGinnis (sean-mcginnis) wrote : Bug Assignee Expired

Unassigning due to no activity for > 6 months.

Changed in cinder:
assignee: Wenjun Wang (wangwenjun) → nobody
Revision history for this message
Gorka Eguileor (gorka) wrote :

This is the expected behavior. When the volume is created the owner is set based on the host, if the host configuration of the volume service is changed and we want it to manage those volumes, then they need to change ownership.

Changing ownership can be accomplished with the "cinder-manage volume update_host" command.

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.