EC2 incorrect snapshot statuses
Bug #1080284 reported by
Attila Fazekas
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Low
|
Michael Still |
Bug Description
I wanted to create volume from a fresh snapshot.
Before I can create a volume I had to wait until it is "completed".
But I got "available".
My other option would be trying the snapshot creation until it succeed. But the incorrect error codes prevent me to distinguish it from other errors.
In the EC2 world the only valid snapshot status are: "pending", "completed", "error".
It differs from the volume statuses.
Before completeness I need to see only "pending" , and should not see "creating".
Changed in nova: | |
status: | New → Triaged |
importance: | Undecided → Low |
tags: | added: ec2 |
Changed in openstack-manuals: | |
milestone: | none → grizzly |
tags: | added: folsom-backport-potential |
no longer affects: | openstack-manuals |
Changed in nova: | |
milestone: | none → grizzly-2 |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | grizzly-2 → 2013.1 |
To post a comment you must log in.
http:// docs.amazonwebs ervices. com/AWSEC2/ latest/ APIReference/ ApiReference- query-DescribeS napshots. html agrees that the valid ec2 statuses are "pending", "completed", and "error".