cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-3211) Object_Store_Refactor - S3 GUI timeout units are unclear
Date Tue, 06 Aug 2013 07:54:47 GMT


ASF subversion and git services commented on CLOUDSTACK-3211:

Commit a764cb91b30cb998aa391a1dc897cbafec26f34a in branch refs/heads/master from [~tpodowd]
[;h=a764cb9 ]

CLOUDSTACK-3211: Add help docs to S3 secondary storage configuration.

When adding an S3 secondary storage, the administrator will
now be shown help for each input field making it friendlier
to use.

Signed-off-by: Prasanna Santhanam <>
(cherry picked from commit 74643c9561b1ea564f180c3780ef762e97e7c10b)

> Object_Store_Refactor - S3 GUI timeout units are unclear
> --------------------------------------------------------
>                 Key: CLOUDSTACK-3211
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>    Affects Versions: 4.2.0
>         Environment: devcloud
> Cloudian or AWS S3 services.
>            Reporter: Thomas O'Dowd
>            Assignee: Thomas O'Dowd
>            Priority: Critical
>             Fix For: 4.2.0
> Connection Timeout:
> Socket Timeout:
> The units for these are unclear. I assumed they were seconds but now I think they might
be milliseconds. 
> When I added S3 secondary storage to a local Cloudian S3 server, I was setting 60 for
the connection timeout and it was ok. However, when I set 60 for the same timeout when adding
the S3 server, I could never manage to upload a template. So I suspect that the connection
was taking longer to setup. No errors are logged which is another problem but when I changed
the timeouts to 60000, I could finally get a template uploaded to AWS.
> The gui should be clear regarding the units and provide help if possible.

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:

View raw message