Return-Path: 
 <dev-return-7663-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 CA9EDE4E9
	for <apmail-deltacloud-dev-archive@www.apache.org>;
 Thu, 24 Jan 2013 17:07:14 +0000 (UTC)
Received: (qmail 33597 invoked by uid 500); 24 Jan 2013 17:07:14 -0000
Delivered-To: apmail-deltacloud-dev-archive@deltacloud.apache.org
Received: (qmail 33577 invoked by uid 500); 24 Jan 2013 17:07:14 -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 33518 invoked by uid 99); 24 Jan 2013 17:07:14 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 24 Jan 2013 17:07:14 +0000
Date: Thu, 24 Jan 2013 17:07:14 +0000 (UTC)
From: "Marios Andreou (JIRA)" <jira@apache.org>
To: dev@deltacloud.apache.org
Message-ID: <JIRA.12627863.1358354580702.185542.1359047234549@arcas>
In-Reply-To: <JIRA.12627863.1358354580702@arcas>
References: <JIRA.12627863.1358354580702@arcas>
Subject: [jira] [Updated] (DTACLOUD-423) Requesting /api/realms against the
 eucalyptus driver fails
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


     [ https://issues.apache.org/jira/browse/DTACLOUD-423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marios Andreou updated DTACLOUD-423:
------------------------------------

    Attachment: 0001-Fix-for-DTACLOUD-423-override-realms-method-for-euca.patch

attached patch implements realms for euca - as per Christian's diagnosis - testing please
                
> Requesting /api/realms against the eucalyptus driver fails
> ----------------------------------------------------------
>
>                 Key: DTACLOUD-423
>                 URL: https://issues.apache.org/jira/browse/DTACLOUD-423
>             Project: DeltaCloud
>          Issue Type: Bug
>          Components: Server
>            Reporter: Christian Karnath
>            Assignee: Marios Andreou
>         Attachments: 0001-Fix-for-DTACLOUD-423-override-realms-method-for-euca.patch
>
>
> Requesting  /api/realms against the eucalyptus driver fails in the current development version. With deltacloud 1.0.2 everything is still fine.
> <?xml version='1.0' encoding='utf-8' ?>
> <error status='500' url='/api/realms'>
>   <kind>backend_error</kind>
>   <backend driver='eucalyptus' provider='ec2=x.x.x.x:8773'>
>     <code>500</code>
>   </backend>
>   <message><![CDATA[Internal Server Error]]></message>
>   <request>
>     <param name='format'>xml</param>
>   </request>
> </error>
> D, [2013-01-16T17:37:29.068507 #26548] DEBUG -- : New Aws::Ec2 using per_thread-connection mode
> D, [2013-01-16T17:37:29.069477 #26548] DEBUG -- : Opening new HTTP connection to x.x.x.x:8773
> W, [2013-01-16T17:37:29.496355 #26548]  WARN -- : ##### Aws::Ec2 returned an error: 412 Precondition Failed
> <?xml version="1.0"?><Response><Errors><Error><Code>412 Precondition Failed</Code><Message>Default binding failed to build a valid message: Missing required object</Message></Error></Errors><RequestID>Default binding failed to build a valid message: Missing required object</RequestID></Response> #####
> W, [2013-01-16T17:37:29.496487 #26548]  WARN -- : ##### Aws::Ec2 request: ..... ####
> E, [2013-01-16T17:37:29.503619 #26548] ERROR -- 500: [Deltacloud::Exceptions::BackendError] Internal Server Error
> 127.0.0.1 - - [16/Jan/2013 17:37:29] "GET /api/realms?format=xml HTTP/1.1" 500 336 0.4448

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira