Re: [jclouds-labs-openstack] Adds support for Rackspace Cloud Big Data (#78)
+ * +/jclouds.osgi.import + /properties + + repositories +repository + idapache-snapshots/id + urlhttps://repository.apache.org/content/repositories/snapshots/url + releases +enabledfalse/enabled + /releases + snapshots +enabledtrue/enabled + /snapshots +/repository + /repositories The snapshots repo is already defined in jclouds-project. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs-openstack/pull/78/files#r9580077
Re: [jclouds-labs-openstack] Adds support for Rackspace Cloud Big Data (#78)
+ scopetest/scope
+/dependency
+dependency
+ groupIdch.qos.logback/groupId
+ artifactIdlogback-classic/artifactId
+ scopetest/scope
+/dependency
+dependency
+ groupIdorg.apache.jclouds.api/groupId
+ artifactIdrackspace-cloudidentity/artifactId
+ version${project.parent.version}/version
+/dependency
+dependency
+ groupIdcom.squareup.okhttp/groupId
+ artifactIdmockwebserver/artifactId
+ version1.2.1/version
The jclouds-project already sets the okhttp version for this, to make sure it
is aligned with the jclouds-okhttp driver. This one should be removed.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-openstack/pull/78/files#r9580105
Re: [jclouds] Revert workaround for Guava issue 1635 (#281)
@demobox +1. Thanks! --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/281#issuecomment-34621511
[jira] [Commented] (JCLOUDS-443) Cannot use rackspace-cloudservers-us or aws-ec2 as the provider
[
https://issues.apache.org/jira/browse/JCLOUDS-443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13896630#comment-13896630
]
Jeremiah Robertson commented on JCLOUDS-443:
Sorry, I have another question. Does the BlobStoreContext take Openstack
credentials or can it take Rackspace Credentials? I get the following
error: java.lang.IllegalArgumentException: api {id=openstack-nova,
name=OpenStack Nova Diablo+ API,
views=[org.jclouds.compute.ComputeServiceContext], endpointName=identity
service url ending in /v2.0/, identityName=${userName},
credentialName=Optional.of(${apiKey}), documentation=
http://docs.rackspace.com/loadbalancers/api/v1.0/clb-devguide/content/index.html,
api=interface org.jclouds.openstack.nova.v2_0.NovaApi, asyncApi=interface
org.jclouds.openstack.nova.v2_0.NovaAsyncApi} not wrappable as
org.jclouds.blobstore.BlobStoreContext; context:
org.jclouds.rest.RestContextorg.jclouds.openstack.nova.v2_0.NovaApi,
org.jclouds.openstack.nova.v2_0.NovaAsyncApi, views:
[org.jclouds.compute.ComputeServiceContext]
On the following piece of code:
BlobStoreContext context = ContextBuilder.newBuilder(providerin)
.credentials(username, apiKey)
.buildView(BlobStoreContext.class);
--
Jeremiah Robertson
Georgia Tech Junior
Aerospace Engineering
Grand Challenges Program
jrs...@gmail.com
417.207.1563
Cannot use rackspace-cloudservers-us or aws-ec2 as the provider
---
Key: JCLOUDS-443
URL: https://issues.apache.org/jira/browse/JCLOUDS-443
Project: jclouds
Issue Type: Bug
Components: jclouds-compute
Affects Versions: 1.7.0
Environment: Ubuntu 13.10, Eclipse
Reporter: Jeremiah Robertson
Priority: Minor
Labels: easyfix
Fix For: 1.7.0
Original Estimate: 1h
Remaining Estimate: 1h
When I go to create the ComputeServiceContext with my credentials and
provider in the rackspace example for creating a server or for the Logging
example (CreateServer.java and Logging.java), it never fully compiles it
cannot find the provider. I used rackspace-cloudservers-us and aws-ec2 as the
2 providers with their set of credentials, and neither worked. Are these
still supported? Please email me back at jrs...@gmail.com if you have aby
ideas on what might be wrong because it worked a week ago and I'm not really
sure whats going on. Thank you!
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Updated] (JCLOUDS-432) Revert Guava/7u51 incompatibility workaround as soon as Guava 1635 is fixed
[ https://issues.apache.org/jira/browse/JCLOUDS-432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Phillips updated JCLOUDS-432: Affects Version/s: 1.6.4 Revert Guava/7u51 incompatibility workaround as soon as Guava 1635 is fixed --- Key: JCLOUDS-432 URL: https://issues.apache.org/jira/browse/JCLOUDS-432 Project: jclouds Issue Type: Improvement Components: jclouds-core Affects Versions: 1.8.0, 1.7.1, 1.6.4 Reporter: Andrew Phillips Assignee: Andrew Phillips Fix For: 1.8.0 Attachments: JCLOUDS-432.patch Workarounds to fix Guava problems that caused JCLOUDS-427 should be removed as soon as the underlying issue [1] is fixed, certainly before the next release if possible. This may required JCLOUDS-415 to be completed, too. Relevant commits: * master: https://git-wip-us.apache.org/repos/asf?p=jclouds.git;a=commit;h=8ff60020f85ae5d9f57e9a25a6342fb7b00e1d2a * 1.7.x: https://git-wip-us.apache.org/repos/asf?p=jclouds.git;a=commit;h=597615977e7e2b10f3680aae24e541a76a1d4606 * 1.6.x: https://git-wip-us.apache.org/repos/asf?p=jclouds.git;h=1b2fb3e [1] https://code.google.com/p/guava-libraries/issues/detail?id=1635 -- This message was sent by Atlassian JIRA (v6.1.5#6160)
Re: [jclouds] Revert workaround for Guava issue 1635 (#281)
Committed to master: [#1](https://git-wip-us.apache.org/repos/asf?p=jclouds.git;a=commit;h=02615adc4f45799d07f61727167b65c87458f573), [#2](https://git-wip-us.apache.org/repos/asf?p=jclouds.git;a=commit;h=4c07702d29de64df45c11819c2cc9d725382b0c2). --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/281#issuecomment-34643091
[jira] [Updated] (JCLOUDS-432) Revert Guava/7u51 incompatibility workaround as soon as Guava 1635 is fixed
[ https://issues.apache.org/jira/browse/JCLOUDS-432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Phillips updated JCLOUDS-432: Attachment: JCLOUDS-432.patch Revert Guava/7u51 incompatibility workaround as soon as Guava 1635 is fixed --- Key: JCLOUDS-432 URL: https://issues.apache.org/jira/browse/JCLOUDS-432 Project: jclouds Issue Type: Improvement Components: jclouds-core Affects Versions: 1.8.0, 1.7.1 Reporter: Andrew Phillips Assignee: Andrew Phillips Attachments: JCLOUDS-432.patch Workarounds to fix Guava problems that caused JCLOUDS-427 should be removed as soon as the underlying issue [1] is fixed, certainly before the next release if possible. This may required JCLOUDS-415 to be completed, too. Relevant commits: * master: https://git-wip-us.apache.org/repos/asf?p=jclouds.git;a=commit;h=8ff60020f85ae5d9f57e9a25a6342fb7b00e1d2a * 1.7.x: https://git-wip-us.apache.org/repos/asf?p=jclouds.git;a=commit;h=597615977e7e2b10f3680aae24e541a76a1d4606 * 1.6.x: https://git-wip-us.apache.org/repos/asf?p=jclouds.git;h=1b2fb3e [1] https://code.google.com/p/guava-libraries/issues/detail?id=1635 -- This message was sent by Atlassian JIRA (v6.1.5#6160)
Re: [jclouds] Revert workaround for Guava issue 1635 (#281)
Another verification build running against master [using 7u51](https://jclouds.ci.cloudbees.com/job/jclouds-java-7u51/36/console) --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/281#issuecomment-34643210
Jenkins build is back to stable : jclouds » jclouds compute core #2536
See https://jclouds.ci.cloudbees.com/job/jclouds/org.apache.jclouds$jclouds-compute/2536/
Re: [jclouds] Revert workaround for Guava issue 1635 (#281)
I asked about a 15.0.1 release in the upstream Guava issue: https://code.google.com/p/guava-libraries/issues/detail?id=1635#c45 --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/281#issuecomment-34651577
[jira] [Commented] (JCLOUDS-443) Cannot use rackspace-cloudservers-us or aws-ec2 as the provider
[ https://issues.apache.org/jira/browse/JCLOUDS-443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13896743#comment-13896743 ] Jeremiah Robertson commented on JCLOUDS-443: Awesome, sounds good. Thank you for your help! -- Jeremiah Robertson Georgia Tech Junior Aerospace Engineering Grand Challenges Program jrs...@gmail.com 417.207.1563 Cannot use rackspace-cloudservers-us or aws-ec2 as the provider --- Key: JCLOUDS-443 URL: https://issues.apache.org/jira/browse/JCLOUDS-443 Project: jclouds Issue Type: Bug Components: jclouds-compute Affects Versions: 1.7.0 Environment: Ubuntu 13.10, Eclipse Reporter: Jeremiah Robertson Priority: Minor Labels: easyfix Fix For: 1.7.0 Original Estimate: 1h Remaining Estimate: 1h When I go to create the ComputeServiceContext with my credentials and provider in the rackspace example for creating a server or for the Logging example (CreateServer.java and Logging.java), it never fully compiles it cannot find the provider. I used rackspace-cloudservers-us and aws-ec2 as the 2 providers with their set of credentials, and neither worked. Are these still supported? Please email me back at jrs...@gmail.com if you have aby ideas on what might be wrong because it worked a week ago and I'm not really sure whats going on. Thank you! -- This message was sent by Atlassian JIRA (v6.1.5#6160)
Re: [jclouds] Revert workaround for Guava issue 1635 (#281)
I asked about a 15.0.1 release in the upstream Guava issue: I saw that, thanks @andrewgaul! Curious to see if there'll be any response... --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/281#issuecomment-34652502
[jira] [Created] (JCLOUDS-459) Limit number of user threads
Andrew Gaul created JCLOUDS-459: --- Summary: Limit number of user threads Key: JCLOUDS-459 URL: https://issues.apache.org/jira/browse/JCLOUDS-459 Project: jclouds Issue Type: Improvement Components: jclouds-core Affects Versions: 1.7.1 Reporter: Andrew Gaul Presently jclouds does not limit the number of user threads. While de-asyncification could address this in the long-term, in the short-term we should protect our users with some sane default. I suggest 20 or 50, the former mirroring the number of IO threads, and the latter sourced from my extensive testing of most blobstore providers. Note that Atmos providers have issues with large numbers of concurrent requests and errors from JCLOUDS-137 will occur. I work around these in my application by setting 10 IO and 10 user threads for Atmos Online and 8 and 8 for Synaptic Atmos. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
Re: [jclouds] Delete objects in a container efficiently. (#214)
Sorry for ignoring this. By default jclouds uses an unlimited number of user threads, set in ```BaseApiMetadata.defaultProperties```. I believe this will cause problems for users of Atmos blobstores. We can work around this by setting a lower number in ```AtmosApiMetadata.defaultProperties```. Previously I have successfully tested with 8 user and 8 IO threads although this depends on the Atmos version and configuration. @shrinandj will run some further tests with the defaults and I will look at a solution to [JCLOUDS-137](https://issues.apache.org/jira/browse/JCLOUDS-137). I also opened [JCLOUDS-459](https://issues.apache.org/jira/browse/JCLOUDS-459) to track adding some limit to all blobstores. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/214#issuecomment-34665263
Jenkins build is back to normal : jclouds-karaf #561
See https://jclouds.ci.cloudbees.com/job/jclouds-karaf/561/
Re: [jclouds-labs-openstack] Adds support for Rackspace Cloud Big Data (#78)
+ * +/jclouds.osgi.import + /properties + + repositories +repository + idapache-snapshots/id + urlhttps://repository.apache.org/content/repositories/snapshots/url + releases +enabledfalse/enabled + /releases + snapshots +enabledtrue/enabled + /snapshots +/repository + /repositories I think the problem here is that, if you check out only the labs-openstack repo, you need to get jclouds-project. If you don't have this snapshot repo, it won't work ;-) --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs-openstack/pull/78/files#r9600707
Re: [jclouds-labs-openstack] Adds support for Rackspace Cloud Big Data (#78)
+ * +/jclouds.osgi.import + /properties + + repositories +repository + idapache-snapshots/id + urlhttps://repository.apache.org/content/repositories/snapshots/url + releases +enabledfalse/enabled + /releases + snapshots +enabledtrue/enabled + /snapshots +/repository + /repositories See response above. This is needed for bootstrapping, I think. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs-openstack/pull/78/files#r9600724
[jclouds] JCLOUDS-137: Retry on HTTP 500 AtmosError 1040 (#285)
You can merge this Pull Request by running: git pull https://github.com/maginatics/jclouds atmos-500-1040 Or you can view, comment on it, or merge it online at: https://github.com/jclouds/jclouds/pull/285 -- Commit Summary -- * JCLOUDS-137: Retry on HTTP 500 AtmosError 1040 -- File Changes -- M apis/atmos/src/main/java/org/jclouds/atmos/config/AtmosRestClientModule.java (2) A apis/atmos/src/main/java/org/jclouds/atmos/handlers/AtmosServerErrorRetryHandler.java (85) A apis/atmos/src/test/java/org/jclouds/atmos/handlers/AtmosServerErrorRetryHandlerTest.java (86) -- Patch Links -- https://github.com/jclouds/jclouds/pull/285.patch https://github.com/jclouds/jclouds/pull/285.diff --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/285
Re: [jclouds] JCLOUDS-137: Retry on HTTP 500 AtmosError 1040 (#285)
@shrinandj relevant to your interests. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/285#issuecomment-34682671
Re: [jclouds] JCLOUDS-137: Retry on HTTP 500 AtmosError 1040 (#285)
The turnaround time on this is INCREDIBLE!! :+1: --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/285#issuecomment-34685027
Re: [jclouds] JCLOUDS-460: Add jitter to avoid thundering herd (#286)
@shrinandj relevant to your interests. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/286#issuecomment-34686120
[jclouds] JCLOUDS-459: Limit maximum user threads (#287)
Previously jclouds could use an unlimited number of threads on its user ExecutorService. While this ExecutorService will go away when we complete deasyncafication, we should prevent jclouds from misbehaving until that time. You can merge this Pull Request by running: git pull https://github.com/maginatics/jclouds max-user-threads Or you can view, comment on it, or merge it online at: https://github.com/jclouds/jclouds/pull/287 -- Commit Summary -- * JCLOUDS-459: Limit maximum user threads -- File Changes -- M core/src/main/java/org/jclouds/apis/internal/BaseApiMetadata.java (2) -- Patch Links -- https://github.com/jclouds/jclouds/pull/287.patch https://github.com/jclouds/jclouds/pull/287.diff --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/287
Re: [jclouds] JCLOUDS-137: Retry on HTTP 500 AtmosError 1040 (#285)
[jclouds » jclouds #827](https://buildhive.cloudbees.com/job/jclouds/job/jclouds/827/) SUCCESS This pull request looks good [(what's this?)](https://www.cloudbees.com/what-is-buildhive) --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/285#issuecomment-34687590
Re: [jclouds] JCLOUDS-137: Retry on HTTP 500 AtmosError 1040 (#285)
[jclouds-java-7-pull-requests #1056](https://jclouds.ci.cloudbees.com/job/jclouds-java-7-pull-requests/1056/) UNSTABLE Looks like there's a problem with this pull request --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/285#issuecomment-34687928
Re: [jclouds] JCLOUDS-137: Retry on HTTP 500 AtmosError 1040 (#285)
[jclouds-pull-requests #584](https://jclouds.ci.cloudbees.com/job/jclouds-pull-requests/584/) SUCCESS This pull request looks good --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/285#issuecomment-34687898
Re: [jclouds] JCLOUDS-137: Retry on HTTP 500 AtmosError 1040 (#285)
Spurious test failure, tracked by [JCLOUDS-429](https://issues.apache.org/jira/browse/JCLOUDS-429). --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/285#issuecomment-34688336
Re: [jclouds] JCLOUDS-459: Limit maximum user threads (#287)
[jclouds-java-7-pull-requests #1058](https://jclouds.ci.cloudbees.com/job/jclouds-java-7-pull-requests/1058/) SUCCESS This pull request looks good --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/287#issuecomment-34694397
Re: [jclouds-labs-openstack] Adds support for Rackspace Cloud Big Data (#78)
+ .clusterType(in.getClusterType())
+ .flavorId(in.getFlavorId())
+ .nodeCount(in.getNodeCount())
+ .postInitScript(in.getPostInitScript());
+ }
+ }
+
+ @Override
+ public int compareTo(CreateCluster that) {
+ return this.getName().compareTo(that.getName());
+ }
+
+ /**
+* Enumerates different types of clusters.
+*/
+ public static enum ClusterType {
This is correct! However to make this PR more testable I have included it for
now.
Ho about removing it when the Cluster Type feature is added?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-openstack/pull/78/files#r9606702
Re: [jclouds-labs-openstack] Adds support for Rackspace Cloud Big Data (#78)
[jclouds-labs-openstack-pull-requests #160](https://jclouds.ci.cloudbees.com/job/jclouds-labs-openstack-pull-requests/160/) SUCCESS This pull request looks good --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs-openstack/pull/78#issuecomment-34715615
[jira] [Created] (JCLOUDS-461) aws-s3 live tests have many bucket does not exist failures
Andrew Gaul created JCLOUDS-461: --- Summary: 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 -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. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (JCLOUDS-461) aws-s3 live tests have many bucket does not exist failures
[ 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
[jira] [Created] (JCLOUDS-462) many aws-ec2 live tests fail
Andrew Gaul created JCLOUDS-462:
---
Summary: many aws-ec2 live tests fail
Key: JCLOUDS-462
URL: https://issues.apache.org/jira/browse/JCLOUDS-462
Project: jclouds
Issue Type: Bug
Components: jclouds-compute
Affects Versions: 1.7.1
Reporter: Andrew Gaul
Fix For: 1.7.2
The many failures make it hard to have confidence in our most popular provider:
$ mvn integration-test -pl :aws-ec2 -Plive
Failed tests:
testAmazonLinuxInstanceStore(org.jclouds.aws.ec2.compute.AWSEC2TemplateBuilderLiveTest):
expected [pv-2013.09.rc-1] but found [pv-2013.09.2]
testFastestTemplateBuilder(org.jclouds.aws.ec2.compute.AWSEC2TemplateBuilderLiveTest):
expected [cc2.8xlarge] but found [c3.8xlarge]
testTemplateBuilderWithLessRegions(org.jclouds.aws.ec2.compute.AWSEC2TemplateBuilderLiveTest):
[]
testTemplateBuilderCanFind(org.jclouds.aws.ec2.compute.AWSEC2TemplateBuilderLiveTest):
no image matched predicate:
And(nullEqualToIsParentOrIsGrandparentOfCurrentLocation(),And(osFamily(centos),osVersion(^6.0$),os64Bit(true)))
testTemplateBuilderCanFind(org.jclouds.aws.ec2.compute.AWSEC2TemplateBuilderLiveTest):
no image matched predicate:
And(nullEqualToIsParentOrIsGrandparentOfCurrentLocation(),And(osFamily(rhel),osVersion(^6.0$),os64Bit(true)))
testExtendedOptionsAndLogin(org.jclouds.aws.ec2.compute.AWSEC2ComputeServiceLiveTest):
request POST https://ec2.us-west-2.amazonaws.com/ HTTP/1.1 failed with code
400, error: AWSError{requestId='006c52a7-ac23-4f92-8e0c-e85df3b1cf8f',
requestToken='null', code='InvalidParameterValue', message='Value (0.3) for
parameter price is invalid. Spot Instance request price 0.3 exceeds your
maximum Spot price limit of 0.08', context='{Response=, Errors=}'}
testTemplateBuilderCannotFind(org.jclouds.aws.ec2.compute.AWSEC2TemplateBuilderLiveTest):
(..)
testTemplateBuilderCannotFind(org.jclouds.aws.ec2.compute.AWSEC2TemplateBuilderLiveTest):
(..)
testTemplateBuilderCannotFind(org.jclouds.aws.ec2.compute.AWSEC2TemplateBuilderLiveTest):
(..)
testTemplateBuilderCannotFind(org.jclouds.aws.ec2.compute.AWSEC2TemplateBuilderLiveTest):
(..)
testTemplateBuilderCannotFind(org.jclouds.aws.ec2.compute.AWSEC2TemplateBuilderLiveTest):
(..)
testTemplateBuilderCanUseImageIdWithoutFetchingAllImages(org.jclouds.aws.ec2.compute.AWSEC2TemplateBuilderLiveTest):
[]
testNoSsh(org.jclouds.aws.ec2.features.AWSKeyPairApiLiveTest): error
runScript on filtered nodes options({loginUser=ec2-user,
loginPasswordPresent=true, loginPrivateKeyPresent=true, runAsRoot=false,
wrapInInitScript=false})(..)
testDescribeSpotPriceHistoryInRegion(org.jclouds.aws.ec2.features.SpotInstanceApiLiveTest):
[region=us-east-1, instanceType=c3.4xlarge, productDescription=Linux/UNIX
(Amazon VPC), spotPrice=1.2, timestamp=Mon Feb 10 17:55:40 PST 2014,
availabilityZone=us-east-1d]
testCreateAndRunAService(org.jclouds.aws.ec2.compute.AWSEC2ComputeServiceLiveTest):
Optional.get() cannot be called on an absent value
testAScriptExecutionAfterBootWithBasicTemplate(org.jclouds.aws.ec2.compute.AWSEC2ComputeServiceLiveTest):
Optional.get() cannot be called on an absent value
testStartCCInstance(org.jclouds.aws.ec2.features.PlacementGroupApiLiveTest):
org.jclouds.compute.RunNodesException: error running 1 node
group(gaulec2cccluster) location(us-east-1) image(ami-0da96764)
size(cc2.8xlarge) options({scriptPresent=true, userDataCksum=2f4a740b})(..)
testCreateTwoNodesWithRunScript(org.jclouds.aws.ec2.compute.AWSEC2ComputeServiceLiveTest):
Optional.get() cannot be called on an absent value
Tests run: 194, Failures: 18, Errors: 0, Skipped: 10
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
Re: [jclouds] JCLOUDS-137: Retry on HTTP 500 AtmosError 1040 (#285)
+ private int retryCountLimit = 5;
+ @Resource
+ protected Logger logger = Logger.NULL;
+
+ public boolean shouldRetryRequest(HttpCommand command, HttpResponse
response) {
+ if (command.getFailureCount() retryCountLimit) {
+ return false;
+ }
+ if (response.getStatusCode() == 500) {
+ byte[] content =
HttpUtils.closeClientButKeepContentStream(response);
+ // Content can be null in the case of HEAD requests
+ if (content != null) {
+try {
+ AtmosError error = utils.parseAtmosErrorFromContent(command,
response,
+new String(content));
+ if (error.getCode() == 1040) { // The server is busy. Please
try again.
I retabulated the 500 error codes and we could retry on most of these, although
I have some concern since I have never experienced these errors:
Error Code | Error Message|
HTTP Status Code and Description
-- | |
1001 | The server encountered an internal error. Please try again. | 500
Internal Server Error
1007 | The server encountered an internal error. Please try again. | 500
Internal Server Error
1013 | The server encountered an internal error. Please try again. | 500
Internal Server Error
1019 | The server encountered an I/O error. Please try again. | 500
Internal Server Error
1020 | The requested resource is missing or could not be found. | 500
Internal Server Error
1024 | The server encountered an internal error. Please try again. | 500
Internal Server Error
1025 | The server encountered an internal error. Please try again. | 500
Internal Server Error
1026 | The server encountered an internal error. Please try again. | 500
Internal Server Error
1027 | The server encountered an internal error. Please try again. | 500
Internal Server Error
1028 | The server encountered an internal error. Please try again. | 500
Internal Server Error
1029 | The server encountered an internal error. Please try again. | 500
Internal Server Error
1040 | The server is busy. Please try again | 500
Internal Server Error
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/285/files#r9613290
