You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Prasanna Santhanam (JIRA)" <ji...@apache.org> on 2013/07/05 10:03:49 UTC

[jira] [Created] (CLOUDSTACK-3374) Object store - bucket names cannot contain periods in them because of older aws sdk

Prasanna Santhanam created CLOUDSTACK-3374:
----------------------------------------------

             Summary: Object store - bucket names cannot contain periods in them because of older aws sdk
                 Key: CLOUDSTACK-3374
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3374
             Project: CloudStack
          Issue Type: Bug
      Security Level: Public (Anyone can view this level - this is the default.)
          Components: Storage Controller
    Affects Versions: 4.2.0
            Reporter: Prasanna Santhanam
            Priority: Critical
             Fix For: 4.2.0


This is a problem with the usage of AWS SDK (1.3.21). The problem is fixed in 1.3.22

Bucket names cannot contain a period in them like DNS names. Adding a bucket with periods will fail with an SSLException

INFO  [amazonaws.http.AmazonHttpClient] (s3-transfer-manager-worker-1:) Unable to execute HTTP request: hostname in certificate didn't match: <acstest.cloudstack.org.s3.amazonaws.com> != <*.s3.amazonaws.com> OR <*.s3.amazonaws.com> OR <s3.amazonaws.com>
javax.net.ssl.SSLException: hostname in certificate didn't match: <acstest.cloudstack.org.s3.amazonaws.com> != <*.s3.amazonaws.com> OR <*.s3.amazonaws.com> OR <s3.amazonaws.com>
	at org.apache.http.conn.ssl.AbstractVerifier.verify(AbstractVerifier.java:228)
	at org.apache.http.conn.ssl.StrictHostnameVerifier.verify(StrictHostnameVerifier.java:61)
	at org.apache.http.conn.ssl.AbstractVerifier.verify(AbstractVerifier.java:149)
	at org.apache.http.conn.ssl.AbstractVerifier.verify(AbstractVerifier.java:130)
	at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:572)
	at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:180)
	at org.apache.http.impl.conn.AbstractPoolEntry.open(AbstractPoolEntry.java:151)
	at org.apache.http.impl.conn.AbstractPooledConnAdapter.open(AbstractPooledConnAdapter.java:125)
	at org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:640)
	at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:479)
	at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:906)
	at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:805)
	at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:784)
	at com.amazonaws.http.AmazonHttpClient.executeHelper(AmazonHttpClient.java:277)
	at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:164)
	at com.amazonaws.services.s3.AmazonS3Client.invoke(AmazonS3Client.java:2863)
	at com.amazonaws.services.s3.AmazonS3Client.initiateMultipartUpload(AmazonS3Client.java:2130)
	at com.amazonaws.services.s3.transfer.internal.UploadCallable.initiateMultipartUpload(UploadCallable.java:224)
	at com.amazonaws.services.s3.transfer.internal.UploadCallable.uploadInParts(UploadCallable.java:119)
	at com.amazonaws.services.s3.transfer.internal.UploadCallable.call(UploadCallable.java:87)
	at com.amazonaws.services.s3.transfer.internal.UploadMonitor.upload(UploadMonitor.java:179)
	at com.amazonaws.services.s3.transfer.internal.UploadMonitor.call(UploadMonitor.java:137)
	at com.amazonaws.services.s3.transfer.internal.UploadMonitor.call(UploadMonitor.java:48)
	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
	at java.util.concurrent.FutureTask.run(FutureTask.java:138)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
	at java.lang.Thread.run(Thread.java:680)



--
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