You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Likitha Shetty (JIRA)" <ji...@apache.org> on 2014/07/16 12:22:04 UTC
[jira] [Resolved] (CLOUDSTACK-7114) [EC2 Query API] Inconsistency
in mapping the "Allocated" state of a Volume to "Available"
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Likitha Shetty resolved CLOUDSTACK-7114.
----------------------------------------
Resolution: Fixed
> [EC2 Query API] Inconsistency in mapping the "Allocated" state of a Volume to "Available"
> ------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-7114
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7114
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: AWSAPI
> Affects Versions: 4.1.0
> Reporter: Likitha Shetty
> Assignee: Likitha Shetty
> Fix For: 4.5.0
>
>
> ================
> Steps to Reproduce:
> ================
> 1. Fire an EC2 REST API: CreateVolume Command. Observe the Status of the Volume in the CreateVolume command's Response Status: Allocated.
> 2. Fire an EC2 REST API: DescribeVolumes Command with the volumeId of the Volume created in Step 1. Observe the Status of the Volume in the DescribeVolumes command's Response Status: Available.
> ==========
> Bug Impact:
> ==========
> "Allocated" is not a valid State as per http://docs.aws.amazon.com/AWSEC2/latest/APIReference/ApiReference-query-CreateVolume.html. Automation expects the value to be a valid value
--
This message was sent by Atlassian JIRA
(v6.2#6252)