CreateVolume API response doesn't match AWS EC2

Bug #767103 reported by Jimmy Bergman
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Fix Released
Medium
Jimmy Bergman

Bug Description

Currently the response looks like:
<?xml version="1.0" ?><CreateVolumeResponse xmlns="http://ec2.amazonaws.com/doc/2011-02-28/"><requestId>7I8G7FE0IROF2VLX-JTX</requestId><volumeSet><item><status>creating (atomiadev, None, None, None)</status><availabilityZone>nova</availabilityZone><displayName/><volumeId>vol-00000003</volumeId><displayDescription/><attachmentSet><item/></attachmentSet><createTime>2011-04-20T11:05:47Z</createTime><size>1</size></item></volumeSet></CreateVolumeResponse>

According to the API documentation it should be:
<?xml version="1.0" ?><CreateVolumeResponse xmlns="http://ec2.amazonaws.com/doc/2011-02-28/"><requestId>7I8G7FE0IROF2VLX-JTX</requestId><status>creating (atomiadev, None, None, None)</status><availabilityZone>nova</availabilityZone><displayName/><volumeId>vol-00000003</volumeId><displayDescription/><attachmentSet><item/></attachmentSet><createTime>2011-04-20T11:05:47Z</createTime><size>1</size></CreateVolumeResponse>

i.e. remove the volumeSet.

Related branches

Thierry Carrez (ttx)
Changed in nova:
assignee: nobody → Jimmy Bergman (jimmy-sigint)
importance: Undecided → Medium
status: New → In Progress
Changed in nova:
status: In Progress → Fix Committed
Thierry Carrez (ttx)
Changed in nova:
milestone: none → diablo-1
Thierry Carrez (ttx)
Changed in nova:
milestone: diablo-1 → 2011.3
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.