jclouds-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Gaul (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (JCLOUDS-461) aws-s3 live tests have many bucket does not exist failures
Date Tue, 11 Feb 2014 01:50:19 GMT

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

Andrew Gaul updated JCLOUDS-461:
--------------------------------

    Description: 
I see many bucket does not exist failures when running:

$ 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

Perhaps we need to disable virtual host buckets by default as we did for JCLOUDS-305 to avoid
DNS settling issues.

  was:
I see many bucket does not exist failures when running:

$ mvn -P '!nexus' 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

Perhaps we need to disable virtual host buckets by default as we did for JCLOUDS-305 to avoid
DNS settling issues.


> 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
>
> I see many bucket does not exist failures when running:
> $ 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
> 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.1.5#6160)

Mime
View raw message