detach volume when call cinder's attach volume fail

Bug #1340709 reported by warewang
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Expired
Undecided
Unassigned

Bug Description

I attach volume on VM, there is a exception occured when call Cinder's attach_volume, Cinder is shown that the volume is not mounted,but i login in to the VM found volume was mounted on the VM.
I think that Nova need to detach volume when the excepiton occured, because,the nova driver has mounted successful before call cinder's attach_volume.
ps:
 1.nova attach a volume;
 2.after nova's driver connect the volume,the nova call the cinder's attach, at this time, the cinder's api get the msg from MQ, but the cinder-volume is reboot.
 3.excute the command(cinder list) the volume is not attach any VM, but login into the VM,
found the volume is attached.

Tags: volumes
warewang (wangguangcai)
Changed in nova:
assignee: nobody → warewang (wangguangcai)
Revision history for this message
Chinmaya Bharadwaj (acbharadwaj) wrote :

Which cinder driver and nova compute driver are you using ?

Revision history for this message
warewang (wangguangcai) wrote :

openstack default driver(libvirt)

warewang (wangguangcai)
summary: - Fix attach volume failure
+ detach volume when call cinder's attach volume fail
warewang (wangguangcai)
description: updated
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to nova (master)

Fix proposed to branch: master
Review: https://review.openstack.org/106958

Changed in nova:
status: New → In Progress
tags: added: volumes
warewang (wangguangcai)
description: updated
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on nova (master)

Change abandoned by Sean Dague (<email address hidden>) on branch: master
Review: https://review.openstack.org/106958
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to nova (master)

Fix proposed to branch: master
Review: https://review.openstack.org/136289

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on nova (master)

Change abandoned by warewang (<email address hidden>) on branch: master
Review: https://review.openstack.org/136289

Revision history for this message
OpenStack Infra (hudson-openstack) wrote :

Change abandoned by Sean Dague (<email address hidden>) on branch: master
Review: https://review.openstack.org/106958
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results.

Revision history for this message
Davanum Srinivas (DIMS) (dims-v) wrote :

both reviews are abandoned. Removing "In Progress" status and assignee.

Changed in nova:
status: In Progress → Confirmed
assignee: warewang (wangguangcai) → nobody
Changed in nova:
assignee: nobody → zhangtralon (zhangchunlong1)
wangxiyuan (wangxiyuan)
Changed in nova:
assignee: zhangtralon (zhangchunlong1) → wangxiyuan (wangxiyuan)
wangxiyuan (wangxiyuan)
Changed in nova:
assignee: wangxiyuan (wangxiyuan) → nobody
zhaobo (zhaobo6)
Changed in nova:
assignee: nobody → zhaobo (zhaobo6)
Changed in nova:
assignee: zhaobo (zhaobo6) → nobody
Revision history for this message
Markus Zoeller (markus_z) (mzoeller) wrote : Cleanup EOL bug report

This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.

If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
  Only still supported release names are valid (LIBERTY, MITAKA, OCATA, NEWTON).
  Valid example: CONFIRMED FOR: LIBERTY

Changed in nova:
status: Confirmed → Expired
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.