update attach status when instance is not a valid UUID

Bug #1192370 reported by John Griffith on 2013-06-18
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Cinder
Medium
John Griffith

Bug Description

Issue reported on ask.openstack (https://ask.openstack.org/question/1828/attach-volume-get-exception-when-instance_uuid-is-invalidbut-the-status-of-volume-is-still-attaching/).

We should do an update on the volume status after we catch the InvalidUUID exception on attach.

Changed in cinder:
importance: Undecided → Medium

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

Changed in cinder:
status: Triaged → In Progress

Reviewed: https://review.openstack.org/33560
Committed: http://github.com/openstack/cinder/commit/4aaa3b64a3ca3050ebed3d748d46facafc09413b
Submitter: Jenkins
Branch: master

commit 4aaa3b64a3ca3050ebed3d748d46facafc09413b
Author: John Griffith <email address hidden>
Date: Tue Jun 18 16:49:13 2013 -0600

    Update attach status when instance id invalid.

    In cinder.manager do_attach we have a check to make sure the
    supplied instance id is a valid UUID which is great, but if it's
    not we just raise and dump out, leaving the volume in an attaching
    state.

    We should update the status to error_attaching in this case and then
    raise/return.

    Fixes bug: 1192370

    Change-Id: Ia759ea7a387544913953ca84e9ed927480c4edfd

Changed in cinder:
status: In Progress → Fix Committed
Thierry Carrez (ttx) on 2013-07-17
Changed in cinder:
status: Fix Committed → Fix Released
Thierry Carrez (ttx) on 2013-10-17
Changed in cinder:
milestone: havana-2 → 2013.2
Alan Pevec (apevec) on 2014-03-31
tags: removed: grizzly-backport-potential
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers