[
https://issues.apache.org/jira/browse/JCLOUDS-461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14335986#comment-14335986
]
Andrew Gaul commented on JCLOUDS-461:
-------------------------------------
Current results:
{noformat}
$ mvn integration-test -pl :aws-s3 -Plive -Paws-s3
...
Failed tests:
AWSS3ContainerLiveTest>BaseContainerLiveTest.testPublicAccess:71->BaseBlobStoreIntegrationTest.assertConsistencyAwareContainerSize:305->BaseBlobStoreIntegrationTest.assertConsistencyAware:248->BaseBlobStoreIntegrationTest.assertConsistencyAware:235
» ContainerNotFound
AWSS3ClientLiveTest.testUseBucketWithUpperCaseName:95 » KeyNotFound
/gaul-blob...
PathBasedContainerLiveTest>BaseContainerLiveTest.testPublicAccessInNonDefaultLocationWithBigBlob:112->BaseContainerLiveTest.runCreateContainerInLocation:125->BaseBlobStoreIntegrationTest.assertConsistencyAwareContainerInLocation:374->BaseBlobStoreIntegrationTest.assertConsistencyAware:248->BaseBlobStoreIntegrationTest.assertConsistencyAware:235
blob gaul-blobstore-4478143323229509054, in location null instead of
{scope=REGION, id=us-standard, description=us-standard, parent=aws-s3,
iso3166Codes=[US]}
AWSS3ClientLiveTest>S3ClientLiveTest.testCopyIfModifiedSince:394 should have
thrown HttpResponseException
{noformat}
> aws-s3 live tests have many bucket does not exist failures
> ----------------------------------------------------------
>
> Key: JCLOUDS-461
> URL: https://issues.apache.org/jira/browse/JCLOUDS-461
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-blobstore
> Reporter: Andrew Gaul
> Assignee: Andrew Gaul
> Priority: Minor
> Labels: aws-s3
> Fix For: 1.9.0
>
>
> I see many bucket does not exist failures when running:
> {noformat}
> $ mvn integration-test -pl :aws-s3 -Plive
> ...
> Failed tests:
> testSignGetUrlOptions(org.jclouds.aws.s3.blobstore.integration.AWSS3BlobSignerLiveTest):
> maginatics-blobstore9.s3.amazonaws.com not found: The specified bucket does
> not exist
>
> testPublicAccess(org.jclouds.aws.s3.blobstore.integration.PathBasedContainerLiveTest):
> maginatics-blobstore-253865899685008831 not found: The specified bucket does
> not exist
>
> testAllLocations(org.jclouds.aws.s3.blobstore.integration.AWSS3ServiceIntegrationLiveTest):
> maginatics-blobstore4376526265318976282.s3.amazonaws.com not found: The
> specified bucket does not exist
>
> testPublicAccess(org.jclouds.aws.s3.blobstore.integration.AWSS3ContainerLiveTest):
> maginatics-blobstore-1286831966318465529.s3.amazonaws.com not found: The
> specified bucket does not exist
> testBucketPayer(org.jclouds.aws.s3.services.AWSBucketsLiveTest):
> maginatics-blobstore-1370573531106075443.s3.amazonaws.com not found: The
> specified bucket does not exist
> testMultipartSynchronously(org.jclouds.aws.s3.AWSS3ClientLiveTest):
> /constitution.txt not found in container
> maginatics-blobstore-4334529154007343555.s3.amazonaws.com: The specified
> bucket does not exist
>
> deleteObject(org.jclouds.aws.s3.blobstore.integration.AWSS3BlobIntegrationLiveTest):
> maginatics-blobstore4723789326031025257.s3.amazonaws.com not found: The
> specified bucket does not exist
> Tests run: 96, Failures: 7, Errors: 0, Skipped: 5
> {noformat}
> Perhaps we need to disable virtual host buckets by default as we did for
> JCLOUDS-305 to avoid DNS settling issues.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
