cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-2104) Failure to attach volume leaves volume in eternal 'Creating' state
Date Fri, 19 Apr 2013 13:23:16 GMT


ASF subversion and git services commented on CLOUDSTACK-2104:

Commit ccc49875dd4c604a2c7303e1e7afd05df72c4a6e in branch refs/heads/4.1 from [~mlsorensen]
[;h=ccc4987 ]

CLOUDSTACK-2104: add state change in createVolume back to Allocated if
anything fails

createVolume changes the volume state from 'Allocated' to 'Creating',
but has no code to change it back to 'Allocated' if anything goes wrong,
despite there already being a path from 'Creating' to 'Allocated' for
volumes, via the OperationFailed event. Adding this in fixes the issue
and avoids leaving disks in an unusable state.

Tested in devcloud-kvm, volume that was larger than primary storage
failed to attack, and went back to 'Allocated' from 'Creating' upon the
failure. I was then able to retry, and delete the disk.

> Failure to attach volume leaves volume in eternal 'Creating' state
> ------------------------------------------------------------------
>                 Key: CLOUDSTACK-2104
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions: 4.1.0
>            Reporter: Marcus Sorensen
>            Assignee: Marcus Sorensen
>            Priority: Critical
>             Fix For: 4.1.0
> I created a disk offering far larger than my primary storage, then created a volume from
it. Upon trying to attach the volume, I noticed that when it failed the disk was left in a
bad state. The disk was left in 'Creating', with no options to delete, retry attach, or anything

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message