Return-Path: 
 <dev-return-4144-apmail-deltacloud-dev-archive=deltacloud.apache.org@deltacloud.apache.org>
X-Original-To: apmail-deltacloud-dev-archive@www.apache.org
Delivered-To: apmail-deltacloud-dev-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id D4F549FD1
	for <apmail-deltacloud-dev-archive@www.apache.org>;
 Thu, 29 Mar 2012 16:56:51 +0000 (UTC)
Received: (qmail 31905 invoked by uid 500); 29 Mar 2012 16:56:50 -0000
Delivered-To: apmail-deltacloud-dev-archive@deltacloud.apache.org
Received: (qmail 31768 invoked by uid 500); 29 Mar 2012 16:56:49 -0000
Mailing-List: contact dev-help@deltacloud.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@deltacloud.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@deltacloud.apache.org>
List-Post: <mailto:dev@deltacloud.apache.org>
List-Id: <dev.deltacloud.apache.org>
Reply-To: dev@deltacloud.apache.org
Delivered-To: mailing list dev@deltacloud.apache.org
Received: (qmail 31749 invoked by uid 99); 29 Mar 2012 16:56:49 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 29 Mar 2012 16:56:49 +0000
X-ASF-Spam-Status: No, hits=-2000.0 required=5.0
	tests=ALL_TRUSTED,T_RP_MATCHES_RCVD
X-Spam-Check-By: apache.org
Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 29 Mar 2012 16:56:47 +0000
Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116])
	by hel.zones.apache.org (Postfix) with ESMTP id 5634034CC72
	for <dev@deltacloud.apache.org>; Thu, 29 Mar 2012 16:56:26 +0000 (UTC)
Date: Thu, 29 Mar 2012 16:56:26 +0000 (UTC)
From: "Ronelle Landy (Created) (JIRA)" <jira@apache.org>
To: dev@deltacloud.apache.org
Message-ID: 
 <485337262.33487.1333040186354.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Created] (DTACLOUD-183) GET
 /api/storage_snapshots/:snapshot_id does not return 'DELETE' as an action -
 xml does not return 'state'
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394

GET /api/storage_snapshots/:snapshot_id does not return 'DELETE' as an action - xml does not return 'state'
-----------------------------------------------------------------------------------------------------------

                 Key: DTACLOUD-183
                 URL: https://issues.apache.org/jira/browse/DTACLOUD-183
             Project: DeltaCloud
          Issue Type: Bug
          Components: Server
         Environment: deltacloud git commit version: a16c34de06776f91fb68cc49e6e1f7d2c815fc01	 - branch 'master' of https://git-wip-us.apache.org/repos/asf/deltacloud
Fedora 16
ec2 provider
            Reporter: Ronelle Landy
            Assignee: David Lutterkort


Two outputs of GET /api/storage_snapshots/:storage_snapshot_id are copied below - first xml and then json.

 - Neither output shows actions listed, although it is possible to delete a snapshot and the GUI does show DELETE as an available action.
 - The json output shows a state item and the xml output does not.

 curl -X GET --user "username:password" "http://localhost:3009/api/storage_snapshots/snap-372caf4d?format=xml"
<?xml version='1.0' encoding='utf-8' ?>
<storage_snapshot href='http://localhost:3009/api/storage_snapshots/snap-372caf4d' id='snap-372caf4d'>
  <created>Mon Mar 19 17:01:58 UTC 2012</created>
  <storage_volume href='http://localhost:3009/api/storage_volumes/vol-efb79583' id='vol-efb79583'></storage_volume>
</storage_snapshot>

[rlandy@localhost /]$ curl -X GET --user username:password" "http://localhost:3009/api/storage_snapshots/snap-372caf4d?format=json"
{"storage_snapshot":{"storage_volume_id":"vol-efb79583","href":"http://localhost:3009/api/storage_snapshots/snap-372caf4d","created":"Mon Mar 19 17:01:58 UTC 2012","state":"completed","id":"snap-372caf4d"}}[rlandy@localhost /]$ 


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira