cloudstack/server
Marcus Sorensen ccc49875dd CLOUDSTACK-2104: add state change in createVolume back to Allocated if
anything fails

Changes:
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.

Testing:
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.
2013-04-19 14:20:57 +01:00
..
conf conf: Add a @ so @MSUSER@ is replaced by "cloud" 2013-04-03 16:54:25 +02:00
resources/com/cloud/upgrade CLOUDSTACK-1818: add a missing file that is missed in previous patch 2013-03-27 13:02:25 +00:00
scripts License header updates for the server folder. 2012-08-03 09:41:27 -04:00
src CLOUDSTACK-2104: add state change in createVolume back to Allocated if 2013-04-19 14:20:57 +01:00
test Changing the number of threads in the test from 1000 to 750. 1000 will more often than not result in build failures due to constraints on the build systems. 2013-04-07 12:08:30 +02:00
pom.xml CLOUDSTACK-1818: make DababaseCreator ready to invoke DatabaseUpgradeChecker, adjust Component startup sequence for integrity checkers 2013-03-27 13:08:03 +00:00