cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Darren Shepherd <>
Subject Re: S3 API broken in 4.2
Date Tue, 22 Oct 2013 18:05:33 GMT
The S3 servlet never initializes.  A NPE is thrown in the init()
method.  Basically there is a silly bug in
CloudStackConfigurationDaoImpl.getConfigValue() that makes it so that
the first call to the method will work, the second call will get a
NPE.  Since EC2 API servlet is set to load-on-startup, the EC2 servlet
always calls CloudStackConfigurationDaoImpl.getConfigValue() first and
it works.  The when you call S3, the init() method calls
getConfigValue() and a NPE is thrown.  The below line needs to be
moved from getConfigValue() to the constructor.

        NameSearch.and("name", NameSearch.entity().getName(),


On Tue, Oct 22, 2013 at 9:22 AM, Min Chen <> wrote:
> Darren, can you be specific what exact s3 API is not working in 4.2?
> Thanks
> -min
> On 10/22/13 5:14 AM, "Sanjeev Neelarapu" <>
> wrote:
>>Hi Darren,
> >From 4.2 onwards we are using addImageStore API with provider parameter
>>for adding any secondary storage provider.
>>-----Original Message-----
>>From: Sebastien Goasguen []
>>Sent: Tuesday, October 22, 2013 2:44 PM
>>Subject: Re: S3 API broken in 4.2
>>On Oct 22, 2013, at 1:22 AM, Chiradeep Vittal
>><> wrote:
>>> Yeah, it was always a tech preview kind of thing. The basic operations
>>> used to work, but since most of the available client tools
>>> (s3cmd/boto/etc) had special workarounds for odd AWS behaviors (in the
>>> return behavior), they would have a hard time working with the S3
>>> implementation in CloudStack which was based entirely on the WSDL.
>>Shall we remove it ? to clean up the code
>>Especially that it is easy to get an S3 store with riakCS, gluster or
>>ceph radosgw.
>>> On 10/21/13 10:16 PM, "Darren S" <> wrote:
>>>> I didn't even know this feature existed until yesterday, so I thought
>>>> I'd try it out, but it seems that the S3 API in CloudStack completely
>>>> doesn't work in 4.2.  Is it supposed to?  Is this an official feature
>>>> or some tech preview type thing?
>>>> Darren

View raw message