Cinder

Hitachi driver: deleting volume failed after creating cloned volume.

Bug #1908792 reported by Kazumasa Nomura
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Cinder
Triaged
Low
Unassigned

Bug Description

In Hitachi Storage, after create cloned volume, it may take time to transition a volume status in the storage, and it may not be possible to delete the cloned source volume immediately.
The following error message will be output.

Dec 19 16:26:39 NomuraCI cinder-volume[3872]: ERROR cinder.volume.drivers.hitachi.hbsd_utils [req-8d554eb2-7bac-4be4-af0b-8dac5168a735 req-e4ae742b-25ea-4ec9-98c8-22f0887cce53 admin None] MSGID0616-E: Failed to delete a pair. (P-VOL: 22007)
Dec 19 16:26:39 NomuraCI cinder-volume[3872]: ERROR cinder.volume.manager [req-8d554eb2-7bac-4be4-af0b-8dac5168a735 req-e4ae742b-25ea-4ec9-98c8-22f0887cce53 admin None] Unable to delete busy volume.: cinder.exception.VolumeIsBusy: deleting volume volume-44cab01c-f019-457b-a15a-90d246558c06 that has snapshot

michael-mcaleer (mmcaleer)
Changed in cinder:
status: New → Triaged
importance: Undecided → Low
tags: added: driver hbsd hitachi
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/cinder 18.0.0.0rc1

This issue was fixed in the openstack/cinder 18.0.0.0rc1 release candidate.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.