Build failed in Jenkins: jclouds-labs #742

2015-01-24 Thread jenkins-no-reply
See 

--
[...truncated 4638 lines...]
[INFO] Exclude: **/src/test/resources/**/*.txt
[INFO] Exclude: **/src/test/resources/**/*.gz
[INFO] Exclude: **/src/test/resources/**/*.xml
[INFO] Exclude: **/src/test/resources/**/*.html
[INFO] Exclude: **/src/test/resources/**/*.iso
[INFO] Exclude: **/LICENSE.txt
[INFO] Exclude: **/header.txt
[INFO] Exclude: **/NOTICE.txt
[INFO] Exclude: **/DISCLAIMER
[INFO] Exclude: **/BUILD.txt
[INFO] Exclude: **/CHANGES.txt
[INFO] Exclude: **/README.md
[INFO] Exclude: **/README.txt
[INFO] Exclude: **/DEPENDENCIES
[INFO] Exclude: **/CONTRIBUTING.md
[INFO] Exclude: **/*json
[INFO] Exclude: **/*readme
[INFO] Exclude: **/*ProviderMetadata
[INFO] Exclude: **/*ApiMetadata
[INFO] Exclude: **/*LoggingModule
[INFO] Exclude: **/*ViewMBeanFactory
[INFO] Exclude: **/target/**
[INFO] Exclude: **/test-output/**
[INFO] Exclude: **/bin/**
[INFO] Exclude: **/.settings/**
[INFO] Exclude: **/.classpath
[INFO] Exclude: **/.dir-locals.el
[INFO] Exclude: **/.project
[INFO] Exclude: **/.idea/**
[INFO] Exclude: **/*.iml
[INFO] Exclude: **/*.eml
[INFO] Exclude: **/*.ipr
[INFO] Exclude: **/*.iws
[INFO] Exclude: **/*.DS_STORE
[INFO] Exclude: **/TAGS
[INFO] Exclude: **/.metadata/**
[INFO] Exclude: **/atlassian-ide-plugin.xml
[INFO] Exclude: **/.DS_Store
[INFO] Exclude: .mailmap
[INFO] Exclude: .git/**
[INFO] Exclude: **/.gitignore
[INFO] Exclude: **/.gitattributes
[INFO] Exclude: .repository/**
[INFO] Exclude: .java-version
[INFO] Exclude: nb-configuration.xml
[INFO] Exclude: nbactions.xml
[INFO] Exclude: .repository/**
[INFO] Exclude: gc.log
[INFO] 127 resources included (use -debug for more details)
Warning:  org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser: Property 
'http://www.oracle.com/xml/jaxp/properties/entityExpansionLimit' is not 
recognized.
Compiler warnings:
  WARNING:  'org.apache.xerces.jaxp.SAXParserImpl: Property 
'http://javax.xml.XMLConstants/property/accessExternalDTD' is not recognized.'
Warning:  org.apache.xerces.parsers.SAXParser: Feature 
'http://javax.xml.XMLConstants/feature/secure-processing' is not recognized.
Warning:  org.apache.xerces.parsers.SAXParser: Property 
'http://javax.xml.XMLConstants/property/accessExternalDTD' is not recognized.
Warning:  org.apache.xerces.parsers.SAXParser: Property 
'http://www.oracle.com/xml/jaxp/properties/entityExpansionLimit' is not 
recognized.
[INFO] Rat check: Summary of files. Unapproved: 0 unknown: 0 generated: 0 
approved: 127 licence.
[INFO] 
[INFO] --- maven-jar-plugin:2.4:test-jar (default) @ cloudsigma2 ---
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-javadoc-plugin:2.9:aggregate-jar (javadoc) @ cloudsigma2 ---
[INFO] 
[INFO] --- maven-javadoc-plugin:2.9:jar (javadoc) @ cloudsigma2 ---
[INFO] 
8 warnings
[WARNING] Javadoc Warnings
[WARNING] 
:40:
 warning - @return tag has no arguments.
[WARNING] 
:49:
 warning - @return tag has no arguments.
[WARNING] 
:58:
 warning - @return tag has no arguments.
[WARNING] 
:67:
 warning - @return tag has no arguments.
[WARNING] 
:76:
 warning - @return tag has no arguments.
[WARNING] 
:86:
 warning - @return tag has no arguments.
[WARNING] 
:96:
 warning - @return tag has no arguments.
[WARNING] 
:106:
 warning - @return tag has no arguments.
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-source-plugin:2.2:jar-no-fork (attach-sources) @ cloudsigma2 
---
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-surefire-plugin:2.17:test (integration) @ cloudsigma2 ---
[JENKINS] Recording test results
[INFO] 
[INFO] --- maven-duplicate-finder-plugin:1.0

Build failed in Jenkins: jclouds-karaf #875

2015-01-24 Thread jenkins-no-reply
See 

--
[...truncated 3469 lines...]
Downloaded: 
https://repository.apache.org/content/repositories/snapshots/org/apache/jclouds/driver/jclouds-apachehc/2.0.0-SNAPSHOT/jclouds-apachehc-2.0.0-20150124.065615-159.jar
 (23 KB at 12.1 KB/sec)
[INFO] Copying bundle: 
org.apache.jclouds.labs:cloudsigma2-sjc:jar:2.0.0-SNAPSHOT
Downloading: 
https://repository-jclouds.forge.cloudbees.com/snapshot/org/apache/jclouds/labs/cloudsigma2-sjc/2.0.0-SNAPSHOT/maven-metadata.xml
Downloading: 
https://repository.apache.org/content/repositories/snapshots/org/apache/jclouds/labs/cloudsigma2-sjc/2.0.0-SNAPSHOT/maven-metadata.xml
Downloading: 
http://download.java.net/maven/2/org/apache/jclouds/labs/cloudsigma2-sjc/2.0.0-SNAPSHOT/maven-metadata.xml
Downloading: 
https://oss.sonatype.org/content/repositories/releases/org/apache/jclouds/labs/cloudsigma2-sjc/2.0.0-SNAPSHOT/maven-metadata.xml
Downloading: 
http://repository.apache.org/snapshots/org/apache/jclouds/labs/cloudsigma2-sjc/2.0.0-SNAPSHOT/maven-metadata.xml
Downloaded: 
https://repository.apache.org/content/repositories/snapshots/org/apache/jclouds/labs/cloudsigma2-sjc/2.0.0-SNAPSHOT/maven-metadata.xml
 (2 KB at 0.4 KB/sec)
Downloaded: 
http://repository.apache.org/snapshots/org/apache/jclouds/labs/cloudsigma2-sjc/2.0.0-SNAPSHOT/maven-metadata.xml
 (2 KB at 0.4 KB/sec)
Downloading: 
https://repository.apache.org/content/repositories/snapshots/org/apache/jclouds/labs/cloudsigma2-sjc/2.0.0-SNAPSHOT/cloudsigma2-sjc-2.0.0-20150124.061441-91.jar
Downloaded: 
https://repository.apache.org/content/repositories/snapshots/org/apache/jclouds/labs/cloudsigma2-sjc/2.0.0-SNAPSHOT/cloudsigma2-sjc-2.0.0-20150124.061441-91.jar
 (256 KB at 127.0 KB/sec)
[INFO] Copying bundle: org.apache.httpcomponents:httpcore-osgi:jar:4.1
Downloading: 
http://repo.cloudbees.com/content/repositories/central/org/apache/httpcomponents/httpcore-osgi/4.1/httpcore-osgi-4.1.jar
Downloaded: 
http://repo.cloudbees.com/content/repositories/central/org/apache/httpcomponents/httpcore-osgi/4.1/httpcore-osgi-4.1.jar
 (334 KB at 9277.4 KB/sec)
[INFO] Copying bundle: 
org.apache.jclouds.provider:rackspace-clouddns-us:jar:2.0.0-SNAPSHOT
Downloading: 
https://repository-jclouds.forge.cloudbees.com/snapshot/org/apache/jclouds/provider/rackspace-clouddns-us/2.0.0-SNAPSHOT/maven-metadata.xml
Downloading: 
https://repository.apache.org/content/repositories/snapshots/org/apache/jclouds/provider/rackspace-clouddns-us/2.0.0-SNAPSHOT/maven-metadata.xml
Downloading: 
https://oss.sonatype.org/content/repositories/releases/org/apache/jclouds/provider/rackspace-clouddns-us/2.0.0-SNAPSHOT/maven-metadata.xml
Downloading: 
http://download.java.net/maven/2/org/apache/jclouds/provider/rackspace-clouddns-us/2.0.0-SNAPSHOT/maven-metadata.xml
Downloading: 
http://repository.apache.org/snapshots/org/apache/jclouds/provider/rackspace-clouddns-us/2.0.0-SNAPSHOT/maven-metadata.xml
Downloaded: 
https://repository.apache.org/content/repositories/snapshots/org/apache/jclouds/provider/rackspace-clouddns-us/2.0.0-SNAPSHOT/maven-metadata.xml
 (1018 B at 0.2 KB/sec)
[WARNING] Could not transfer metadata 
org.apache.jclouds.provider:rackspace-clouddns-us:2.0.0-SNAPSHOT/maven-metadata.xml
 from/to apache.snapshots (http://repository.apache.org/snapshots): Failed to 
transfer file: 
http://repository.apache.org/snapshots/org/apache/jclouds/provider/rackspace-clouddns-us/2.0.0-SNAPSHOT/maven-metadata.xml.
 Return code is: 502 , ReasonPhrase:Proxy Error.
Downloading: 
https://repository.apache.org/content/repositories/snapshots/org/apache/jclouds/provider/rackspace-clouddns-us/2.0.0-SNAPSHOT/rackspace-clouddns-us-2.0.0-20150124.070809-159.jar
Downloaded: 
https://repository.apache.org/content/repositories/snapshots/org/apache/jclouds/provider/rackspace-clouddns-us/2.0.0-SNAPSHOT/rackspace-clouddns-us-2.0.0-20150124.070809-159.jar
 (13 KB at 10.7 KB/sec)
[INFO] Copying bundle: org.apache.jclouds:jclouds-blobstore:jar:2.0.0-SNAPSHOT
[INFO] Copying bundle: org.apache.jclouds.api:cloudwatch:jar:2.0.0-SNAPSHOT
Downloading: 
https://repository-jclouds.forge.cloudbees.com/snapshot/org/apache/jclouds/api/cloudwatch/2.0.0-SNAPSHOT/maven-metadata.xml
Downloading: 
https://repository.apache.org/content/repositories/snapshots/org/apache/jclouds/api/cloudwatch/2.0.0-SNAPSHOT/maven-metadata.xml
Downloading: 
https://oss.sonatype.org/content/repositories/releases/org/apache/jclouds/api/cloudwatch/2.0.0-SNAPSHOT/maven-metadata.xml
Downloading: 
http://download.java.net/maven/2/org/apache/jclouds/api/cloudwatch/2.0.0-SNAPSHOT/maven-metadata.xml
Downloading: 
http://repository.apache.org/snapshots/org/apache/jclouds/api/cloudwatch/2.0.0-SNAPSHOT/maven-metadata.xml
Downloaded: 
https://repository.apache.org/content/repositories/snapshots/org/apache/jclouds/api/cloudwatch/2.0.0-SNAPSHOT/maven-metadata.xml
 (1002 B at 0.6 KB/sec)
[WARNING] Could not transfer metadata 
org.apache.jc

[jira] [Updated] (JCLOUDS-407) JClouds (HPCloud) documentation is not upto date

2015-01-24 Thread Andrew Gaul (JIRA)

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

Andrew Gaul updated JCLOUDS-407:

Component/s: (was: jclouds-core)
 docs

> JClouds (HPCloud) documentation is not upto date
> 
>
> Key: JCLOUDS-407
> URL: https://issues.apache.org/jira/browse/JCLOUDS-407
> Project: jclouds
>  Issue Type: Improvement
>  Components: docs
>Affects Versions: 1.6.2
>Reporter: uma maheswari mohandoss
>  Labels: documentation
>
> The documentation needs an update according to the latest jclouds version. It 
> would seem that a new user who just followed instructions on JClouds website 
> and tried to run simplest example they have would fail miserably to achieve 
> anything.  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (JCLOUDS-493) Extend TemplateOptions and CreateServerOptions to support fixed private IPs and more

2015-01-24 Thread Andrew Gaul (JIRA)

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

Andrew Gaul updated JCLOUDS-493:

Labels:   (was: features)

> Extend TemplateOptions and CreateServerOptions to support fixed private IPs 
> and more
> 
>
> Key: JCLOUDS-493
> URL: https://issues.apache.org/jira/browse/JCLOUDS-493
> Project: jclouds
>  Issue Type: Improvement
>  Components: jclouds-compute
>Affects Versions: 1.7.1
> Environment: jClouds 1.7.1
>Reporter: Jeffrey Nguyen
>Assignee: Jeffrey Nguyen
>
> Hi jClouds Devs,
> I'm currently working an enhancement related to recent enhancements to 
> support networks in jClouds compute layer [1] and OpenStack nova [2].  In 
> jClouds 1.7.1, both of these are invoked via the method 
> "networks(Iterable networks)".   I believe the intention is to set a 
> list of network UUIDs.
> For each network UUID, I want to be able to assign a fixed private IP 
> address, and possibly MAC address and port number.  [3] Below is an example 
> of how I assign (network UUID, fixed private IP) tuples for the 3 network 
> interfaces when creating a server in OpenStack. 
> Ideally, we need a more generic API like "TemplateOptions 
> networks(Iterable> networks)".   This will support all of 
> the network attributes instead of just the network UUID.
> Obviously Java does not allow the above overloaded method because we already 
> have a "networks(Iterable networks)" in the existing implementation.
> I'd like to propose we create a new method 
> "networkConfig(Iterable> networkConfig)" and deprecate  
> "networks(Iterable networks)".   This will allow each individual Iaas 
> to take time to migrate to the new API.
> What I like about the new API is that since it's a Map, it'll take any 
> network attributes supported by the underlined Iaas.  All we need to do is 
> specify the attribute names in the JSON payload (not hard-coded in the code). 
>  For example, when I apply this new API against OpenStack nova, I can specify 
> network UUID, fix_ip, and port UUID for each interface.   Also, if any new 
> attribute is introduced under networks, we'll get it for free with this new 
> enhancement.
> Please let me know what you think.
> Regards,
> -Jeffrey
> [1] https://issues.apache.org/jira/browse/JCLOUDS-416
> [2] https://issues.apache.org/jira/browse/JCLOUDS-202
> [3] OpenStack JSON payload for creating server with network uuid and fixed 
> private IP:
> "{"server":{"name":"testp-e12","imageRef":"66dac7ce-992c-43a4-b765-029c0b6fc1fe","flavorRef":"1d89ff82-5981-4a14-91e5-fc769f82a2f9","metadata":{"jclouds-group":"testp"},"key_name":"test","security_groups":[{"name":"default"}],"user_data":"U0VSVk...VAx","networks":[{"uuid":"fb9c21f4-0672-48b2-8279-77334bb63a53","fixed_ip":"172.16.0.10"},{"uuid":"aa1809a2-c32d-4eb8-a5c5-e46f692416e0","fixed_ip":"172.16.1.11"},{"uuid":"1e43f86f-4165-4f2e-8017-dd4cfb5548b0","fixed_ip":"172.16.2.12"}]}}"



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (JCLOUDS-407) JClouds (HPCloud) documentation is not upto date

2015-01-24 Thread Andrew Gaul (JIRA)

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

Andrew Gaul updated JCLOUDS-407:

Labels:   (was: documentation)

> JClouds (HPCloud) documentation is not upto date
> 
>
> Key: JCLOUDS-407
> URL: https://issues.apache.org/jira/browse/JCLOUDS-407
> Project: jclouds
>  Issue Type: Improvement
>  Components: docs
>Affects Versions: 1.6.2
>Reporter: uma maheswari mohandoss
>
> The documentation needs an update according to the latest jclouds version. It 
> would seem that a new user who just followed instructions on JClouds website 
> and tried to run simplest example they have would fail miserably to achieve 
> anything.  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (JCLOUDS-536) Support Nova Quota Sets Extension API

2015-01-24 Thread Andrew Gaul (JIRA)

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

Andrew Gaul updated JCLOUDS-536:

Labels: openstack-nova  (was: openstack)

> Support Nova Quota Sets Extension API
> -
>
> Key: JCLOUDS-536
> URL: https://issues.apache.org/jira/browse/JCLOUDS-536
> Project: jclouds
>  Issue Type: Improvement
>  Components: jclouds-compute
>Affects Versions: 1.8.0
>Reporter: Jeremy Daggett
>  Labels: openstack-nova
>
> JCLOUDS-526 proposes the removal of the legacy Nova QuotaClassApi, however 
> the QuotaApi currently maps to the "os-quota-class" OpenStack Nova Extension.
> The domain object for Quota needs to be updated to reflect the added/removed 
> fields. 
> volumes, gigabytes, and cores have been removed.
> quota_set, fixed_ips, and injected_file_path_bytes have been added.
> Unit/Live Tests will need to be updated



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (JCLOUDS-408) JClouds(HPCloud): Server list fails with JSON error.

2015-01-24 Thread Andrew Gaul (JIRA)

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

Andrew Gaul updated JCLOUDS-408:

Labels: hpcloud-compute  (was: test)

> JClouds(HPCloud): Server list fails with JSON error.
> 
>
> Key: JCLOUDS-408
> URL: https://issues.apache.org/jira/browse/JCLOUDS-408
> Project: jclouds
>  Issue Type: Bug
>  Components: jclouds-compute
>Affects Versions: 1.6.2
>Reporter: uma maheswari mohandoss
>  Labels: hpcloud-compute
>
> JClouds - HPCloud.
> JClouds version tried:  1.6.1, 16.2, 1.6.2-incubating.
> List server fails when there is a VM booted from volume.
> Consider VM that is booted from volume, this VM is then listed by fetching 
> list from servers/details - such server has no image. However in JSON 
> response image is returned as empty string.  Finally resulting in JSON error.
> Note:  If server list DOES NOT contain VM booted from volume, NOT hitting 
> this issue.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (JCLOUDS-445) bootstrap script should fail the create vm if it has errors

2015-01-24 Thread Andrew Gaul (JIRA)

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

Andrew Gaul updated JCLOUDS-445:

Labels: bootstrap-script  (was: bootstrap-script jclouds)

> bootstrap script should fail the create vm if it has errors
> ---
>
> Key: JCLOUDS-445
> URL: https://issues.apache.org/jira/browse/JCLOUDS-445
> Project: jclouds
>  Issue Type: Bug
>  Components: jclouds-compute
>Affects Versions: 1.7.0, 1.8.0
>Reporter: Izek Greenfield
>  Labels: bootstrap-script
>
> I see error in the bootstrap script and Jclouds return the machine as OK.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (JCLOUDS-793) make blobstore put operations report server errors via HttpResponseException

2015-01-24 Thread Andrew Gaul (JIRA)

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

Andrew Gaul updated JCLOUDS-793:

Labels:   (was: features)

> make blobstore put operations report server errors via HttpResponseException
> 
>
> Key: JCLOUDS-793
> URL: https://issues.apache.org/jira/browse/JCLOUDS-793
> Project: jclouds
>  Issue Type: Improvement
>  Components: jclouds-blobstore
>Affects Versions: 1.8.1
>Reporter: Daniel Hsueh
>
> observed with openstack-swift 1.8.1 ObjectApi.put()
> if the server responds with a 4xx/5xx response, the put() call returns null 
> for the etag
> would it be more useful if there was an HttpResponseException were thrown, 
> with the actual request, response, and response code available?  as of now, 
> the null response only indicates that an etag was not found in the response, 
> not that the whole request failed
> I observe that a failure to communicate (e.g. BackoffLimitedRetryHandler 
> running through its retires) will result in an HttpResponseException
> there may also be an issue with consistency -- from perusing the 
> AzureBlobClient and S3Client code it seems like an HttpException("did not 
> receive ETag") would be thrown, and not a null etag
> I would also propose that GETs report 4xx/5xx responses via 
> HttpResponseException as well
> I realize this is a major departure from existing behavior, perhaps this 
> exception-reporting-on-error could be enabled via an override?
> thank you



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (JCLOUDS-134) Update links on official website

2015-01-24 Thread Andrew Gaul (JIRA)

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

Andrew Gaul updated JCLOUDS-134:

Labels:   (was: documentation)

> Update links on official website
> 
>
> Key: JCLOUDS-134
> URL: https://issues.apache.org/jira/browse/JCLOUDS-134
> Project: jclouds
>  Issue Type: Task
>  Components: docs
>Reporter: Diogo Monteiro
>
> Some links are broken on the official website.
> The ones I found were:
> http://jclouds.incubator.apache.org/documentation/devguides/
> -Issue tracker
> -Google code
> I haven't checked all the other ones but some might be broken as well.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (JCLOUDS-700) OpenStack Nova AvailabilityZone class missing "hosts" field

2015-01-24 Thread Andrew Gaul (JIRA)

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

Andrew Gaul updated JCLOUDS-700:

Labels: openstack-nova  (was: api openstack)

> OpenStack Nova AvailabilityZone class missing "hosts" field
> ---
>
> Key: JCLOUDS-700
> URL: https://issues.apache.org/jira/browse/JCLOUDS-700
> Project: jclouds
>  Issue Type: Bug
>  Components: jclouds-compute
>Affects Versions: 1.8.0
>Reporter: Jeremy Daggett
>  Labels: openstack-nova
> Fix For: 2.0.0
>
>
> The {{hosts}} field is not taken into consideration by the 
> {{AvailabilityZone}} class as documented 
> [here|https://github.com/openstack/nova/blob/grizzly-eol/nova/api/openstack/compute/contrib/availability_zone.py#L138].
> The following actions should be taken to ensure the correct implementation:
> * Add the {{hosts}} field to {{AvailabilityZone}} class.
> * Move {{AvailabilityZone}} and {{ZoneState}} from the deprecated 
> {{org.jclouds.openstack.nova.v2_0.domain.zonescoped}} package to the correct 
> {{org.jclouds.openstack.nova.v2_0.domain}} package.
> * Change {{ZoneState.available()}} to {{ZoneState.isAvailable()}}.
> * Update expect/live tests.
> * Deprecate where appropriate.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (JCLOUDS-468) Nova needs to handle key pair creation better in the ComputeService

2015-01-24 Thread Andrew Gaul (JIRA)

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

Andrew Gaul updated JCLOUDS-468:

Labels: openstack-nova  (was: openstack)

> Nova needs to handle key pair creation better in the ComputeService
> ---
>
> Key: JCLOUDS-468
> URL: https://issues.apache.org/jira/browse/JCLOUDS-468
> Project: jclouds
>  Issue Type: Improvement
>  Components: jclouds-compute
>Reporter: Everett Toews
>Priority: Minor
>  Labels: openstack-nova
>
> Nova needs a strategy so it behaves more like 
> org.jclouds.aws.ec2.compute.strategy.CreateKeyPairPlacementAndSecurityGroupsAsNeededAndReturnRunOptions.createNewKeyPairUnlessUserSpecifiedOtherwise()
>  
> Right now it only has 
> org.jclouds.openstack.nova.v2_0.compute.loaders.CreateUniqueKeyPair which 
> does not examine TemplateOptions to determine what to do. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (JCLOUDS-456) Cinder clone volume

2015-01-24 Thread Andrew Gaul (JIRA)

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

Andrew Gaul updated JCLOUDS-456:

Labels: openstack-cinder rackspace  (was: openstack rackspace)

> Cinder clone volume
> ---
>
> Key: JCLOUDS-456
> URL: https://issues.apache.org/jira/browse/JCLOUDS-456
> Project: jclouds
>  Issue Type: Improvement
>  Components: jclouds-compute
>Reporter: Everett Toews
>Priority: Minor
>  Labels: openstack-cinder, rackspace
>
> Support cloning an existing volume.
> API doc: 
> http://docs.rackspace.com/cbs/api/v1.0/cbs-devguide/content/POST_createVolume_v1__tenant_id__volumes_v1__tenant_id__volumes.html)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (JCLOUDS-345) Add examples for multi-region BlobStore

2015-01-24 Thread Andrew Gaul (JIRA)

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

Andrew Gaul updated JCLOUDS-345:

Component/s: docs

> Add examples for multi-region BlobStore
> ---
>
> Key: JCLOUDS-345
> URL: https://issues.apache.org/jira/browse/JCLOUDS-345
> Project: jclouds
>  Issue Type: New Feature
>  Components: docs, jclouds-examples
>Affects Versions: 1.7.0
>Reporter: Jeremy Daggett
>Priority: Minor
>
> Examples should cover most operations with the first multi-region BlobStore 
> (Swift) [1] and be consistent with other jclouds examples. 
> [1] 
> /openstack-swift/src/main/java/org/jclouds/openstack/swift/v1/blobstore/RegionScopedSwiftBlobStore.java



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (JCLOUDS-714) Refactor TemplateOptions getGroups() method naming

2015-01-24 Thread Andrew Gaul (JIRA)

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

Andrew Gaul updated JCLOUDS-714:

Labels:   (was: compute)

> Refactor TemplateOptions getGroups() method naming
> --
>
> Key: JCLOUDS-714
> URL: https://issues.apache.org/jira/browse/JCLOUDS-714
> Project: jclouds
>  Issue Type: Bug
>  Components: jclouds-compute
>Affects Versions: 1.6.0, 1.7.0, 1.8.0
>Reporter: Jeremy Daggett
>Priority: Minor
>
> The {{TemplateOptions.getGroups()}} method name is vague and confusing. It 
> relates to a  _security group_, and should be aptly renamed to 
> {{TemplateOptions.getSecurityGroups()}}. The old {{getGroups()}} accessor 
> should be deprecated and slated for removal in 2.0.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (JCLOUDS-345) Add examples for multi-region BlobStore

2015-01-24 Thread Andrew Gaul (JIRA)

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

Andrew Gaul updated JCLOUDS-345:

Labels:   (was: documentation)

> Add examples for multi-region BlobStore
> ---
>
> Key: JCLOUDS-345
> URL: https://issues.apache.org/jira/browse/JCLOUDS-345
> Project: jclouds
>  Issue Type: New Feature
>  Components: docs, jclouds-examples
>Affects Versions: 1.7.0
>Reporter: Jeremy Daggett
>Priority: Minor
>
> Examples should cover most operations with the first multi-region BlobStore 
> (Swift) [1] and be consistent with other jclouds examples. 
> [1] 
> /openstack-swift/src/main/java/org/jclouds/openstack/swift/v1/blobstore/RegionScopedSwiftBlobStore.java



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (JCLOUDS-454) NovaComputeService should query extensions to see if security groups are supported

2015-01-24 Thread Andrew Gaul (JIRA)

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

Andrew Gaul updated JCLOUDS-454:

Labels: openstack-nova  (was: openstack)

> NovaComputeService should query extensions to see if security groups are 
> supported
> --
>
> Key: JCLOUDS-454
> URL: https://issues.apache.org/jira/browse/JCLOUDS-454
> Project: jclouds
>  Issue Type: Bug
>  Components: jclouds-compute
>Reporter: Everett Toews
>Priority: Minor
>  Labels: openstack-nova
> Fix For: 2.0.0
>
>
> Right now NovaSecurityGroupExtension is injected into the NovaComputeService 
> via NovaComputeServiceContextModule. This is effectively an assumption that 
> all OpenStack clouds support security groups. Some may not.
> NovaComputeService should override getSecurityGroupExtension() and query 
> extensions to see if security groups are supported.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (JCLOUDS-718) Compute TemplateOptions.getGroups() is ambigous

2015-01-24 Thread Andrew Gaul (JIRA)

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

Andrew Gaul updated JCLOUDS-718:

Labels: security-groups  (was: compute security-groups)

> Compute TemplateOptions.getGroups() is ambigous
> ---
>
> Key: JCLOUDS-718
> URL: https://issues.apache.org/jira/browse/JCLOUDS-718
> Project: jclouds
>  Issue Type: Bug
>  Components: jclouds-compute
>Affects Versions: 1.8.0
>Reporter: Jeremy Daggett
>Priority: Minor
>  Labels: security-groups
>
> From a user's perspective, this method is quite confusing. What does this 
> method _actually_ return? Groups of IPs, groups of availability zones... What 
> specifically? 
> In the {{TemplateOptions}} class, the {{getGroups()}} method lacks intent and 
> should be aptly renamed to {{getSecurityGroups()}}. The method should be 
> deprecated and replaced with the suggested method signature, and marked for 
> removal in 2.0.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (JCLOUDS-767) Creating multiple spot instances fails. Status polling too frequent?

2015-01-24 Thread Andrew Gaul (JIRA)

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

Andrew Gaul updated JCLOUDS-767:

Labels: DOS Spot aws-ec2  (was: AWS DOS Spot)

> Creating multiple spot instances fails. Status polling too frequent?
> 
>
> Key: JCLOUDS-767
> URL: https://issues.apache.org/jira/browse/JCLOUDS-767
> Project: jclouds
>  Issue Type: Bug
>  Components: jclouds-compute
>Affects Versions: 1.8.1
> Environment: AWS, Spot instances, CoreOS
>Reporter: Yaron Rosenbaum
>Priority: Blocker
>  Labels: DOS, Spot, aws-ec2
>
> My program creates spot instances (see 'addNode' below).
> Recently, in some cases I've been getting "RequestResourceCountExceeded" 
> error (see below).
> I am creating multiple nodes on multiple threads (3).
> It appears that jClouds is polling node status too frequently, and AWS 
> perceives this as a DOS attack. AWS polling queries fail on "The amount of 
> data you requested and frequency of requests together exceed the levels 
> allowed by the Spot service".
> jClouds interprets this as a failure to create, whereas this is just a 
> failure to poll.
> The spot requests, however, are valid - and eventually fulfilled, but because 
> of this error - they are never properly configured by jClouds, and in fact - 
> are just left as orphans.
> This scenario, in turn, ends up creating more and more nodes - endlessly, all 
> left as orphans (but costing dear $).
> So,
> 1) This specific error should not be interpreted as failure
> 2) The polling interval should be increased, or at least configurable
> 3) Maybe some sort of exponential backoff should be used in case this error 
> happens
> 4) Failed spot requests should verify that the spot request is cancelled
> (the code below happens on 3 threads, concurrently)
>   public ComputeMetadata addNode(Template template) throws 
> RunNodesException {
>   ComputeMetadata result = 
> Iterables.getOnlyElement(getComputeService().createNodesInGroup(getGroupName(),
>  1, template));
>   LOG.info("Node \"{}\" created", result.getName());
> 10:06:02.795 [main] INFO  io.multicloud.controller.AWSProvider - quorum is 
> missing 3 nodes
> 10:06:03.077 [main] INFO  i.m.controller.CloudProviderImpl - Adding 3 nodes
> 10:06:04.113 [pool-3-thread-1] WARN  jclouds.compute - << not api visible 
> instances([{region=us-east-1, name=sir-02gebgm2}])
> 10:06:04.342 [pool-3-thread-3] WARN  jclouds.compute - << not api visible 
> instances([{region=us-east-1, name=sir-02gez2h5}])
> 10:06:04.460 [pool-3-thread-2] WARN  jclouds.compute - << not api visible 
> instances([{region=us-east-1, name=sir-02ghn9t2}])
> 10:06:17.853 [user thread 1] ERROR jclouds.compute - << problem customizing 
> node(us-east-1/sir-02gez2h5): 
> org.jclouds.aws.AWSResponseException: request POST 
> https://ec2.us-east-1.amazonaws.com/ HTTP/1.1 failed with code 400, error: 
> AWSError{requestId='c5ffce45-02c3-4443-b4c2-42cfe3e2a7ef', 
> requestToken='null', code='RequestResourceCountExceeded', message='the amount 
> of data you requested and frequency of requests together exceed the levels 
> allowed by the Spot service', context='{Response=, Errors=}'}
>   at 
> org.jclouds.aws.handlers.ParseAWSErrorFromXmlContent.handleError(ParseAWSErrorFromXmlContent.java:75)
>  ~[sts-1.8.1.jar:1.8.1]
>   at 
> org.jclouds.http.handlers.DelegatingErrorHandler.handleError(DelegatingErrorHandler.java:65)
>  ~[jclouds-core-1.8.1.jar:1.8.1]
>   at 
> org.jclouds.http.internal.BaseHttpCommandExecutorService.shouldContinue(BaseHttpCommandExecutorService.java:128)
>  ~[jclouds-core-1.8.1.jar:1.8.1]
>   at 
> org.jclouds.http.internal.BaseHttpCommandExecutorService.invoke(BaseHttpCommandExecutorService.java:98)
>  ~[jclouds-core-1.8.1.jar:1.8.1]
>   at 
> org.jclouds.rest.internal.InvokeHttpMethod.invoke(InvokeHttpMethod.java:90) 
> ~[jclouds-core-1.8.1.jar:1.8.1]
>   at 
> org.jclouds.rest.internal.InvokeHttpMethod.apply(InvokeHttpMethod.java:73) 
> ~[jclouds-core-1.8.1.jar:1.8.1]
>   at 
> org.jclouds.rest.internal.InvokeHttpMethod.apply(InvokeHttpMethod.java:44) 
> ~[jclouds-core-1.8.1.jar:1.8.1]
>   at 
> org.jclouds.reflect.FunctionalReflection$FunctionalInvocationHandler.handleInvocation(FunctionalReflection.java:117)
>  ~[jclouds-core-1.8.1.jar:1.8.1]
>   at 
> com.google.common.reflect.AbstractInvocationHandler.invoke(AbstractInvocationHandler.java:87)
>  ~[guava-17.0.jar:na]
>   at $Proxy70.describeSpotInstanceRequestsInRegion(Unknown Source) 
> ~[na:na]
>   at 
> org.jclouds.aws.ec2.compute.strategy.AWSEC2GetNodeMetadataStrategy.getRunningInstanceInRegion(AWSEC2GetNodeMetadataStrategy.java:53)
>  ~[aws-ec2-1.8.1.jar:1.8.1]
>   at 
> org.jclouds.ec2.compute.strategy.EC2GetNod

[jira] [Updated] (JCLOUDS-728) Support nested API @Delegate annotations

2015-01-24 Thread Andrew Gaul (JIRA)

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

Andrew Gaul updated JCLOUDS-728:

Labels: apis  (was: apis core)

> Support nested API @Delegate annotations
> 
>
> Key: JCLOUDS-728
> URL: https://issues.apache.org/jira/browse/JCLOUDS-728
> Project: jclouds
>  Issue Type: Improvement
>  Components: jclouds-core
>Affects Versions: 1.8.0
>Reporter: Jeremy Daggett
>Priority: Critical
>  Labels: apis
>
> Currently, the {{@Delegate}} annotation can only delegate to a single API and 
> there is a need to support multiple levels of delegation.
> For example, a {{TopLevelApi}} needs to delegate to a {{FeatureApi}}, that in 
> turn delegates to a {{SubFeatureApi}}:
> {code:java}
> public interface TopLevelApi {
> @Delegate
> FeatureApi getFeatureApi();
> }
> public interface FeatureApi {
> @Delegate 
> SubFeatureApi getSubFeatureApi();
> }
> public interface SubFeatureApi {
> // subfeature specific APIs
> String doSomething();
> }
> {code}
> {{HttpApiModule}} uses {{BinderUtils.bindHttpApi}} to bind a top level API 
> which can only delegate one level deep at this time.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (JCLOUDS-559) Upgrade to JAX-RS 2.0

2015-01-24 Thread Andrew Gaul (JIRA)

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

Andrew Gaul updated JCLOUDS-559:

Labels:   (was: patch)

> Upgrade to JAX-RS 2.0
> -
>
> Key: JCLOUDS-559
> URL: https://issues.apache.org/jira/browse/JCLOUDS-559
> Project: jclouds
>  Issue Type: Improvement
>  Components: jclouds-core
>Affects Versions: 2.0.0
>Reporter: Jeremy Daggett
>
> Upgrade the JAX-RS library from 1.1.1 to the latest 2.0 version:
> javax.ws.rs » jsr311-api
> http://mvnrepository.com/artifact/javax.ws.rs/jsr311-api/1.1.1
> javax.ws.rs » javax.ws.rs-api
> http://mvnrepository.com/artifact/javax.ws.rs/javax.ws.rs-api/2.0



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (JCLOUDS-270) softlayer: Expose port-speed in template. Set default to 100Mbps.

2015-01-24 Thread Andrew Gaul (JIRA)

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

Andrew Gaul updated JCLOUDS-270:

Labels: softlayer  (was: provider provider-softlayer)

> softlayer: Expose port-speed in template. Set default to 100Mbps.
> -
>
> Key: JCLOUDS-270
> URL: https://issues.apache.org/jira/browse/JCLOUDS-270
> Project: jclouds
>  Issue Type: Improvement
>  Components: jclouds-compute
> Environment: api.softlayer.com/rest/v3/
>Reporter: David Toy
>Priority: Minor
>  Labels: softlayer
>
> Currently jclouds:softlayer does not expose virtualguest.port-speed to the 
> template builder.
> Adding this would make SoftLayer easier to use.
> Additionally: the default template[1] in jclouds:softlayer specifies the new 
> instances are created with a 10Mbps public and private port.
> There is no price difference between 10Mbps and 100Mbps ports[2][3] (both 
> free, 1G ports not free), so 100Mbps would be a better default value.
> 1. 
> https://github.com/jclouds/jclouds/blob/master/providers/softlayer/src/main/java/org/jclouds/softlayer/SoftLayerProviderMetadata.java#L69
> 2. http://www.softlayer.com/cloudlayer/build-your-own-cloud
> 3. https://manage.softlayer.com/Sales/orderHourlyComputingInstance



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (JCLOUDS-266) softlayer: Use alpha region ids, instead of numeric (ams01 vs 265592)

2015-01-24 Thread Andrew Gaul (JIRA)

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

Andrew Gaul updated JCLOUDS-266:

Labels: softlayer  (was: provider provider-softlayer)

> softlayer: Use alpha region ids, instead of numeric (ams01 vs 265592)
> -
>
> Key: JCLOUDS-266
> URL: https://issues.apache.org/jira/browse/JCLOUDS-266
> Project: jclouds
>  Issue Type: Improvement
>  Components: jclouds-compute
> Environment: api.softlayer.com/rest/v3/
>Reporter: David Toy
>Priority: Minor
>  Labels: softlayer
>
> Currently when using softlayer regions must be specified using a numeric 
> 'locationId'.
> In addition to the numeric id SoftLayer make a human readable 'name' 
> available for each region.
> Can jclouds:softlayer switch to using the easier alphanumeric name to specify 
> a region? 
> e.g. jclouds.softlayer:ams01, rather than jclouds.softlayer:265592.
> JSON from SoftLayer:
> {"id":265592,"longName":"Amsterdam 
> 1","name":"ams01","locationAddress":{"accountId":1,"address1":"Paul van 
> Vlissingenstraat 
> 16","city":"Amsterdam","contactName":"SoftLayer","country":"NL","description":"Amsterdam
>  - AMS01","id":3322,"isActive":1,"locationId":265592,"postalCode":"1096 
> BK","type":{"createDate":"2010-04-06T04:49:15+01:00","id":1,"keyName":"SOFTLAYER_DATACENTER","name":"SoftLayer
>  Datacenter (accepts customer DTS 
> shipments)"}},"regions":[{"description":"AMS01 - Amsterdam - Western 
> Europe","keyname":"AMSTERDAM","sortOrder":11}]}]}"



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


Re: [jclouds-labs-google] Configure GCS consistency model as "STRICT" (#121)

2015-01-24 Thread Andrew Gaul
Closed #121.

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-google/pull/121#event-224143476

[jira] [Created] (JCLOUDS-811) Update google-compute-engine driver to reflect recent API changes

2015-01-24 Thread Ajay Viswanathan (JIRA)
Ajay Viswanathan created JCLOUDS-811:


 Summary: Update google-compute-engine driver to reflect recent API 
changes
 Key: JCLOUDS-811
 URL: https://issues.apache.org/jira/browse/JCLOUDS-811
 Project: jclouds
  Issue Type: Bug
  Components: jclouds-labs-google
Affects Versions: 1.8.1, 1.8.0
 Environment: Debian, Mac
Reporter: Ajay Viswanathan


GCE recently added shutdown ability for its instances. When an instance is in 
shutdown state, a REST API call to the instance returns no STATE information 
and common operations like listNodes() fail showing a null exception while 
parsing INPUT for "status".

Could this be fixed so as to ignore stopped instances or atleast not crash any 
calls made using jclouds.

ps: There also seems to be something funny at the GCE backend. If I stop an 
instance and fetch node metadata usign Jclouds, I get a terminated for the 
node, which is what is expected. After say, an hour or so, it no longer returns 
anything and crashes the call throwing the same error described above. 

I'd like to know if this error is replicated on another cloud account.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


Re: [jclouds] Fix for JCLOUDS-655 (#626)

2015-01-24 Thread monitorjbl
Whoops! Fixed it, sorry about that.

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/626#issuecomment-71325502

Jenkins build is back to normal : jclouds-labs-aws » Apache jclouds :: AWS :: Glacier API #342

2015-01-24 Thread jenkins-no-reply
See 




Jenkins build is back to normal : jclouds-labs » jclouds CloudSigma v2 API #743

2015-01-24 Thread jenkins-no-reply
See 




Jenkins build is back to normal : jclouds-labs-openstack » jclouds openstack-marconi api #608

2015-01-24 Thread jenkins-no-reply
See 




[jira] [Updated] (JCLOUDS-811) Update google-compute-engine driver to reflect recent API changes

2015-01-24 Thread Andrew Gaul (JIRA)

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

Andrew Gaul updated JCLOUDS-811:

Labels: google-compute-engine  (was: )

> Update google-compute-engine driver to reflect recent API changes
> -
>
> Key: JCLOUDS-811
> URL: https://issues.apache.org/jira/browse/JCLOUDS-811
> Project: jclouds
>  Issue Type: Bug
>  Components: jclouds-compute, jclouds-labs-google
>Affects Versions: 1.8.0, 1.8.1
> Environment: Debian, Mac
>Reporter: Ajay Viswanathan
>  Labels: google-compute-engine
>
> GCE recently added shutdown ability for its instances. When an instance is in 
> shutdown state, a REST API call to the instance returns no STATE information 
> and common operations like listNodes() fail showing a null exception while 
> parsing INPUT for "status".
> Could this be fixed so as to ignore stopped instances or atleast not crash 
> any calls made using jclouds.
> ps: There also seems to be something funny at the GCE backend. If I stop an 
> instance and fetch node metadata usign Jclouds, I get a terminated for the 
> node, which is what is expected. After say, an hour or so, it no longer 
> returns anything and crashes the call throwing the same error described 
> above. 
> I'd like to know if this error is replicated on another cloud account.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (JCLOUDS-811) Update google-compute-engine driver to reflect recent API changes

2015-01-24 Thread Andrew Gaul (JIRA)

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

Andrew Gaul updated JCLOUDS-811:

Component/s: jclouds-compute

> Update google-compute-engine driver to reflect recent API changes
> -
>
> Key: JCLOUDS-811
> URL: https://issues.apache.org/jira/browse/JCLOUDS-811
> Project: jclouds
>  Issue Type: Bug
>  Components: jclouds-compute, jclouds-labs-google
>Affects Versions: 1.8.0, 1.8.1
> Environment: Debian, Mac
>Reporter: Ajay Viswanathan
>  Labels: google-compute-engine
>
> GCE recently added shutdown ability for its instances. When an instance is in 
> shutdown state, a REST API call to the instance returns no STATE information 
> and common operations like listNodes() fail showing a null exception while 
> parsing INPUT for "status".
> Could this be fixed so as to ignore stopped instances or atleast not crash 
> any calls made using jclouds.
> ps: There also seems to be something funny at the GCE backend. If I stop an 
> instance and fetch node metadata usign Jclouds, I get a terminated for the 
> node, which is what is expected. After say, an hour or so, it no longer 
> returns anything and crashes the call throwing the same error described 
> above. 
> I'd like to know if this error is replicated on another cloud account.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (JCLOUDS-96) address aws-s3 live test failures

2015-01-24 Thread ASF subversion and git services (JIRA)

[ 
https://issues.apache.org/jira/browse/JCLOUDS-96?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14290770#comment-14290770
 ] 

ASF subversion and git services commented on JCLOUDS-96:


Commit affad9fa3b66e45c4b7c0bb2483e959dc0f5341a in jclouds's branch 
refs/heads/master from [~gaul]
[ https://git-wip-us.apache.org/repos/asf?p=jclouds.git;h=affad9f ]

JCLOUDS-96: JCLOUDS-351: Fix S3 copy if tests

Use correct options in testCopyIfUnmodifiedSince, use looser time
bounds, and ensure that tests throw HttpResponseException when
expected.


> address aws-s3 live test failures
> -
>
> Key: JCLOUDS-96
> URL: https://issues.apache.org/jira/browse/JCLOUDS-96
> Project: jclouds
>  Issue Type: Bug
>  Components: jclouds-blobstore
>Affects Versions: 1.6.0
>Reporter: Andrew Gaul
>Assignee: Andrew Gaul
>  Labels: aws-s3
> Fix For: 1.9.0
>
>
> This should not block the 1.6.1 release but we should address these:
> Failed tests:   
> testCopyIfModifiedSince(org.jclouds.aws.s3.AWSS3ClientLiveTest): request PUT 
> https://gaul-blobstore8.s3.amazonaws.com/pears HTTP/1.1 failed with code 412, 
> error: AWSError{requestId='2C3067DD0F517071', 
> requestToken='BCYXQkcYsJn5a4ICR+sfMg0DDkfG3nJSESzGlZv1xjbW6yb/1ohcCNHHQYY7A3VJ',
>  code='PreconditionFailed', message='At least one of the pre-conditions you 
> specified did not hold', 
> context='{Condition=x-amz-copy-source-If-Modified-Since, 
> HostId=BCYXQkcYsJn5a4ICR+sfMg0DDkfG3nJSESzGlZv1xjbW6yb/1ohcCNHHQYY7A3VJ}'}
>   
> testDirectory(org.jclouds.aws.s3.blobstore.integration.AWSS3ContainerIntegrationLiveTest):
>  [[type=RELATIVE_PATH, id=null, name=directory, location={scope=REGION, 
> id=us-standard, description=us-standard, parent=aws-s3, iso3166Codes=[US]}, 
> uri=https://gaul-blobstore18.s3.amazonaws.com/directory/, userMetadata={}]]
>   
> testPutFileParallel(org.jclouds.aws.s3.blobstore.integration.AWSS3BlobIntegrationLiveTest):
>  putFileParallel, completed: 0/10, errors: 0, rate: 3000ms/op
>   
> testPublicAccessInNonDefaultLocation(org.jclouds.aws.s3.blobstore.integration.AWSS3ContainerLiveTest):
>  Validation on 'public abstract 
> com.google.common.util.concurrent.ListenableFuture 
> org.jclouds.s3.S3AsyncClient.putBucketInRegion(java.lang.String,java.lang.String,org.jclouds.s3.options.PutBucketOptions[])[us-standard,
>  
> gaul-blobstore166105864973802436317-88465623902772003-29211719058811089442391555942423291658,
>  [Lorg.jclouds.s3.options.PutBucketOptions;@6954bfe]' didn't pass:(..)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (JCLOUDS-351) testCopyIfModifiedSince fails against AWS-S3

2015-01-24 Thread ASF subversion and git services (JIRA)

[ 
https://issues.apache.org/jira/browse/JCLOUDS-351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14290771#comment-14290771
 ] 

ASF subversion and git services commented on JCLOUDS-351:
-

Commit affad9fa3b66e45c4b7c0bb2483e959dc0f5341a in jclouds's branch 
refs/heads/master from [~gaul]
[ https://git-wip-us.apache.org/repos/asf?p=jclouds.git;h=affad9f ]

JCLOUDS-96: JCLOUDS-351: Fix S3 copy if tests

Use correct options in testCopyIfUnmodifiedSince, use looser time
bounds, and ensure that tests throw HttpResponseException when
expected.


> testCopyIfModifiedSince fails against AWS-S3
> 
>
> Key: JCLOUDS-351
> URL: https://issues.apache.org/jira/browse/JCLOUDS-351
> Project: jclouds
>  Issue Type: Bug
>  Components: jclouds-blobstore
>Affects Versions: 1.6.3
>Reporter: Andrew Gaul
>  Labels: aws-s3
> Fix For: 1.9.0
>
>
> {noformat}
> testCopyIfModifiedSince(org.jclouds.aws.s3.AWSS3ClientLiveTest)  Time 
> elapsed: 2.929 sec  <<< FAILURE!
> org.jclouds.aws.AWSResponseException: request PUT 
> https://gaul-blobstore1330667931334611482.s3.amazonaws.com/pears HTTP/1.1 
> failed with code 412, error: AWSError{requestId='...', requestToken='...', 
> code='PreconditionFailed', message='At least one of the pre-conditions you 
> specified did not hold', 
> context='{Condition=x-amz-copy-source-If-Modified-Since, HostId=...}'}
> at 
> org.jclouds.aws.handlers.ParseAWSErrorFromXmlContent.handleError(ParseAWSErrorFromXmlContent.java:76)
> at 
> org.jclouds.http.handlers.DelegatingErrorHandler.handleError(DelegatingErrorHandler.java:67)
> at 
> org.jclouds.http.internal.BaseHttpCommandExecutorService.shouldContinue(BaseHttpCommandExecutorService.java:180)
> at 
> org.jclouds.http.internal.BaseHttpCommandExecutorService.invoke(BaseHttpCommandExecutorService.java:150)
> at 
> org.jclouds.rest.internal.InvokeSyncToAsyncHttpMethod.invoke(InvokeSyncToAsyncHttpMethod.java:131)
> at 
> org.jclouds.rest.internal.InvokeSyncToAsyncHttpMethod.apply(InvokeSyncToAsyncHttpMethod.java:97)
> at 
> org.jclouds.rest.internal.InvokeSyncToAsyncHttpMethod.apply(InvokeSyncToAsyncHttpMethod.java:58)
> at 
> org.jclouds.rest.internal.DelegatesToInvocationFunction.handle(DelegatesToInvocationFunction.java:157)
> at 
> org.jclouds.rest.internal.DelegatesToInvocationFunction.invoke(DelegatesToInvocationFunction.java:124)
> at com.sun.proxy.$Proxy56.copyObject(Unknown Source)
> at 
> org.jclouds.s3.S3ClientLiveTest.testCopyIfModifiedSince(S3ClientLiveTest.java:374)
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


Build failed in Jenkins: jclouds-karaf #877

2015-01-24 Thread jenkins-no-reply
See 

--
[...truncated 934 lines...]
[INFO] --- maven-site-plugin:3.3:attach-descriptor (attach-descriptor) @ 
urlhandler ---
[INFO] 
[INFO] --- apache-rat-plugin:0.10:check (default) @ urlhandler ---
[INFO] 51 implicit excludes (use -debug for more details).
[INFO] Exclude: **/LICENSE.txt
[INFO] Exclude: **/header.txt
[INFO] Exclude: **/NOTICE.txt
[INFO] Exclude: **/DISCLAIMER
[INFO] Exclude: **/BUILD.txt
[INFO] Exclude: **/CHANGES.txt
[INFO] Exclude: **/README.md
[INFO] Exclude: **/README.txt
[INFO] Exclude: **/DEPENDENCIES
[INFO] Exclude: **/CONTRIBUTING.md
[INFO] Exclude: .git/**
[INFO] Exclude: **/.gitignore
[INFO] Exclude: **/*.json
[INFO] Exclude: **/*.log*
[INFO] Exclude: **/TODO
[INFO] Exclude: .mailmap
[INFO] Exclude: .idea/**
[INFO] Exclude: **/*.iml
[INFO] Exclude: **/.project
[INFO] Exclude: **/.classpath
[INFO] Exclude: **/.settings/**
[INFO] Exclude: **/.checkstyle
[INFO] Exclude: **/target/**
[INFO] Exclude: .repository/**
[INFO] Exclude: **/src/main/resources/**/*.txt
[INFO] 3 resources included (use -debug for more details)
Warning:  org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser: Property 
'http://www.oracle.com/xml/jaxp/properties/entityExpansionLimit' is not 
recognized.
Compiler warnings:
  WARNING:  'org.apache.xerces.jaxp.SAXParserImpl: Property 
'http://javax.xml.XMLConstants/property/accessExternalDTD' is not recognized.'
Warning:  org.apache.xerces.parsers.SAXParser: Feature 
'http://javax.xml.XMLConstants/feature/secure-processing' is not recognized.
Warning:  org.apache.xerces.parsers.SAXParser: Property 
'http://javax.xml.XMLConstants/property/accessExternalDTD' is not recognized.
Warning:  org.apache.xerces.parsers.SAXParser: Property 
'http://www.oracle.com/xml/jaxp/properties/entityExpansionLimit' is not 
recognized.
[INFO] Rat check: Summary of files. Unapproved: 0 unknown: 0 generated: 0 
approved: 3 licence.
[INFO] 
[INFO] --- maven-install-plugin:2.5.1:install (default-install) @ urlhandler ---
[INFO] Installing 

 to 
/home/jenkins/.m2/repository/org/apache/jclouds/karaf/urlhandler/2.0.0-SNAPSHOT/urlhandler-2.0.0-SNAPSHOT.jar
[INFO] Installing 
 to 
/home/jenkins/.m2/repository/org/apache/jclouds/karaf/urlhandler/2.0.0-SNAPSHOT/urlhandler-2.0.0-SNAPSHOT.pom
[INFO] 
[INFO] --- maven-bundle-plugin:2.1.0:install (default-install) @ urlhandler ---
[INFO] Installing 
org/apache/jclouds/karaf/urlhandler/2.0.0-SNAPSHOT/urlhandler-2.0.0-SNAPSHOT.jar
[INFO] Writing OBR metadata
[INFO] 
[INFO] --- maven-deploy-plugin:2.8.1:deploy (default-deploy) @ urlhandler ---
Downloading: 
https://repository.apache.org/content/repositories/snapshots/org/apache/jclouds/karaf/urlhandler/2.0.0-SNAPSHOT/maven-metadata.xml
Downloaded: 
https://repository.apache.org/content/repositories/snapshots/org/apache/jclouds/karaf/urlhandler/2.0.0-SNAPSHOT/maven-metadata.xml
 (790 B at 1.9 KB/sec)
Uploading: 
https://repository.apache.org/content/repositories/snapshots/org/apache/jclouds/karaf/urlhandler/2.0.0-SNAPSHOT/urlhandler-2.0.0-20150124.200605-210.jar
Uploaded: 
https://repository.apache.org/content/repositories/snapshots/org/apache/jclouds/karaf/urlhandler/2.0.0-SNAPSHOT/urlhandler-2.0.0-20150124.200605-210.jar
 (22 KB at 24.2 KB/sec)
Uploading: 
https://repository.apache.org/content/repositories/snapshots/org/apache/jclouds/karaf/urlhandler/2.0.0-SNAPSHOT/urlhandler-2.0.0-20150124.200605-210.pom
Uploaded: 
https://repository.apache.org/content/repositories/snapshots/org/apache/jclouds/karaf/urlhandler/2.0.0-SNAPSHOT/urlhandler-2.0.0-20150124.200605-210.pom
 (3 KB at 2.2 KB/sec)
Downloading: 
https://repository.apache.org/content/repositories/snapshots/org/apache/jclouds/karaf/urlhandler/maven-metadata.xml
Downloaded: 
https://repository.apache.org/content/repositories/snapshots/org/apache/jclouds/karaf/urlhandler/maven-metadata.xml
 (595 B at 0.9 KB/sec)
Uploading: 
https://repository.apache.org/content/repositories/snapshots/org/apache/jclouds/karaf/urlhandler/2.0.0-SNAPSHOT/maven-metadata.xml
Uploaded: 
https://repository.apache.org/content/repositories/snapshots/org/apache/jclouds/karaf/urlhandler/2.0.0-SNAPSHOT/maven-metadata.xml
 (790 B at 1.0 KB/sec)
Uploading: 
https://repository.apache.org/content/repositories/snapshots/org/apache/jclouds/karaf/urlhandler/maven-metadata.xml
Uploaded: 
https://repository.apache.org/content/repositories/snapshots/org/apache/jclouds/karaf/urlhandler/maven-metadata.xml
 (595 B at 0.4 KB/sec)
[INFO] 
[INFO] --- maven-bundle-plugin:2.1.0:deploy (default-deploy) @ urlhandler ---
[INFO] Remote OBR update disabled (enable with -DremoteOBR)
Started calculate disk usage of build
Finished Calculation of disk usage of build in 0 seconds
Started calculate disk usage of workspace
Finished Calculati

Build failed in Jenkins: jclouds-labs #744

2015-01-24 Thread jenkins-no-reply
See 

--
[...truncated 1312 lines...]
[INFO] 
[INFO] --- maven-bundle-plugin:2.3.7:bundle (default-bundle) @ docker ---
[INFO] 
[INFO] --- maven-site-plugin:3.3:attach-descriptor (attach-descriptor) @ docker 
---
[INFO] 
[INFO] --- apache-rat-plugin:0.10:check (default) @ docker ---
[INFO] 51 implicit excludes (use -debug for more details).
[INFO] Exclude: **/src/test/resources/**/*.sh
[INFO] Exclude: **/src/test/resources/**/*.bat
[INFO] Exclude: **/src/test/resources/**/*.cmd
[INFO] Exclude: **/src/test/resources/**/*.txt
[INFO] Exclude: **/src/test/resources/**/*.gz
[INFO] Exclude: **/src/test/resources/**/*.xml
[INFO] Exclude: **/src/test/resources/**/*.html
[INFO] Exclude: **/src/test/resources/**/*.iso
[INFO] Exclude: **/LICENSE.txt
[INFO] Exclude: **/header.txt
[INFO] Exclude: **/NOTICE.txt
[INFO] Exclude: **/DISCLAIMER
[INFO] Exclude: **/BUILD.txt
[INFO] Exclude: **/CHANGES.txt
[INFO] Exclude: **/README.md
[INFO] Exclude: **/README.txt
[INFO] Exclude: **/DEPENDENCIES
[INFO] Exclude: **/CONTRIBUTING.md
[INFO] Exclude: **/*json
[INFO] Exclude: **/*readme
[INFO] Exclude: **/*ProviderMetadata
[INFO] Exclude: **/*ApiMetadata
[INFO] Exclude: **/*LoggingModule
[INFO] Exclude: **/*ViewMBeanFactory
[INFO] Exclude: **/target/**
[INFO] Exclude: **/test-output/**
[INFO] Exclude: **/bin/**
[INFO] Exclude: **/.settings/**
[INFO] Exclude: **/.classpath
[INFO] Exclude: **/.dir-locals.el
[INFO] Exclude: **/.project
[INFO] Exclude: **/.idea/**
[INFO] Exclude: **/*.iml
[INFO] Exclude: **/*.eml
[INFO] Exclude: **/*.ipr
[INFO] Exclude: **/*.iws
[INFO] Exclude: **/*.DS_STORE
[INFO] Exclude: **/TAGS
[INFO] Exclude: **/.metadata/**
[INFO] Exclude: **/atlassian-ide-plugin.xml
[INFO] Exclude: **/.DS_Store
[INFO] Exclude: .mailmap
[INFO] Exclude: .git/**
[INFO] Exclude: **/.gitignore
[INFO] Exclude: **/.gitattributes
[INFO] Exclude: .repository/**
[INFO] Exclude: .java-version
[INFO] Exclude: nb-configuration.xml
[INFO] Exclude: nbactions.xml
[INFO] Exclude: .repository/**
[INFO] Exclude: gc.log
[INFO] 67 resources included (use -debug for more details)
Warning:  org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser: Property 
'http://www.oracle.com/xml/jaxp/properties/entityExpansionLimit' is not 
recognized.
Compiler warnings:
  WARNING:  'org.apache.xerces.jaxp.SAXParserImpl: Property 
'http://javax.xml.XMLConstants/property/accessExternalDTD' is not recognized.'
Warning:  org.apache.xerces.parsers.SAXParser: Feature 
'http://javax.xml.XMLConstants/feature/secure-processing' is not recognized.
Warning:  org.apache.xerces.parsers.SAXParser: Property 
'http://javax.xml.XMLConstants/property/accessExternalDTD' is not recognized.
Warning:  org.apache.xerces.parsers.SAXParser: Property 
'http://www.oracle.com/xml/jaxp/properties/entityExpansionLimit' is not 
recognized.
[INFO] Rat check: Summary of files. Unapproved: 0 unknown: 0 generated: 0 
approved: 65 licence.
[INFO] 
[INFO] --- maven-jar-plugin:2.4:test-jar (default) @ docker ---
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-javadoc-plugin:2.9:aggregate-jar (javadoc) @ docker ---
[INFO] 
[INFO] --- maven-javadoc-plugin:2.9:jar (javadoc) @ docker ---
[INFO] 
3 warnings
[WARNING] Javadoc Warnings
[WARNING] 
:55:
 warning - @return tag has no arguments.
[WARNING] 
:65:
 warning - @return tag has no arguments.
[WARNING] 
:241:
 warning - Tag @see: can't find cpuShares(int) in 
org.jclouds.docker.compute.options.DockerTemplateOptions
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-source-plugin:2.2:jar-no-fork (attach-sources) @ docker ---
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-surefire-plugin:2.17:test (integration) @ docker ---
[JENKINS] Recording test results[INFO] 
[INFO] --- maven-duplicate-finder-plugin:1.0.5:check (default) @ docker ---

[INFO] Checking compile classpath
[INFO] Checking runtime classpath
[INFO] Checking test classpath
[INFO] 
[INFO] --- maven-checkstyle-plugin:2.13:check (default) @ docker ---
[INFO] 
[INFO] 
[INFO] --- modernizer-maven-plugin:1.2.2:modernizer (modernizer) @ docker ---
[INFO] 
[INFO] --- maven-install-plugin:2.4:install (default-install) @ docker ---
[INFO] Installing 

 

Jenkins build is back to normal : jclouds-labs-aws #343

2015-01-24 Thread jenkins-no-reply
See 



Jenkins build is back to normal : jclouds-labs-aws #343

2015-01-24 Thread jenkins-no-reply
See 



Build failed in Jenkins: jclouds-labs » jclouds docker API #744

2015-01-24 Thread jenkins-no-reply
See 


--
[...truncated 221 lines...]
INFO: MockWebServer[45048] done accepting connections: Socket closed
[pool-13-thread-1] Test 
testKillContainer(org.jclouds.docker.features.ContainerApiMockTest) succeeded: 
136ms
Test suite progress: tests succeeded: 23, failed: 0, skipped: 0.
Starting test 
testRemoveContainer(org.jclouds.docker.features.ContainerApiMockTest)
Jan 24, 2015 3:05:51 PM com.squareup.okhttp.mockwebserver.MockWebServer$2 
acceptConnections
INFO: MockWebServer[46534] done accepting connections: Socket closed
[pool-13-thread-3] Test 
testListContainers(org.jclouds.docker.features.ContainerApiMockTest) succeeded: 
136ms
Test suite progress: tests succeeded: 24, failed: 0, skipped: 0.
Starting test 
testRestartContainer(org.jclouds.docker.features.ContainerApiMockTest)
Jan 24, 2015 3:05:51 PM com.squareup.okhttp.mockwebserver.MockWebServer$2 
execute
INFO: MockWebServer[60070] starting to accept connections
Jan 24, 2015 3:05:51 PM com.squareup.okhttp.mockwebserver.MockWebServer$3 
processOneRequest
INFO: MockWebServer[59053] received request: GET 
/v1.15/containers/json?all=true HTTP/1.1 and responded: HTTP/1.1 200 OK
Jan 24, 2015 3:05:51 PM com.squareup.okhttp.mockwebserver.MockWebServer$2 
execute
INFO: MockWebServer[49446] starting to accept connections
Jan 24, 2015 3:05:51 PM com.squareup.okhttp.mockwebserver.MockWebServer$2 
acceptConnections
INFO: MockWebServer[59053] done accepting connections: Socket closed
Jan 24, 2015 3:05:51 PM com.squareup.okhttp.mockwebserver.MockWebServer$3 
processOneRequest
INFO: MockWebServer[36995] received request: GET /v1.15/containers/json 
HTTP/1.1 and responded: HTTP/1.1 404 OK
[pool-13-thread-2] Test 
testListAllContainers(org.jclouds.docker.features.ContainerApiMockTest) 
succeeded: 162ms
Test suite progress: tests succeeded: 25, failed: 0, skipped: 0.
Starting test 
testStartContainer(org.jclouds.docker.features.ContainerApiMockTest)
Jan 24, 2015 3:05:51 PM com.squareup.okhttp.mockwebserver.MockWebServer$2 
execute
INFO: MockWebServer[36280] starting to accept connections
Jan 24, 2015 3:05:51 PM com.squareup.okhttp.mockwebserver.MockWebServer$2 
acceptConnections
INFO: MockWebServer[36995] done accepting connections: Socket closed
[pool-13-thread-5] Test 
testListNonexistentContainers(org.jclouds.docker.features.ContainerApiMockTest) 
succeeded: 127ms
Test suite progress: tests succeeded: 26, failed: 0, skipped: 0.
Starting test 
testStopContainer(org.jclouds.docker.features.ContainerApiMockTest)
Jan 24, 2015 3:05:51 PM com.squareup.okhttp.mockwebserver.MockWebServer$2 
execute
INFO: MockWebServer[46039] starting to accept connections
Jan 24, 2015 3:05:51 PM com.squareup.okhttp.mockwebserver.MockWebServer$3 
processOneRequest
INFO: MockWebServer[57131] received request: POST /v1.15/containers/1/pause 
HTTP/1.1 and responded: HTTP/1.1 204 OK
Jan 24, 2015 3:05:51 PM com.squareup.okhttp.mockwebserver.MockWebServer$2 
acceptConnections
INFO: MockWebServer[57131] done accepting connections: Socket closed
[pool-13-thread-4] Test 
testPauseContainer(org.jclouds.docker.features.ContainerApiMockTest) succeeded: 
122ms
Test suite progress: tests succeeded: 27, failed: 0, skipped: 0.
Starting test 
testUnpauseContainer(org.jclouds.docker.features.ContainerApiMockTest)
Jan 24, 2015 3:05:51 PM com.squareup.okhttp.mockwebserver.MockWebServer$2 
execute
INFO: MockWebServer[51070] starting to accept connections
Jan 24, 2015 3:05:52 PM com.squareup.okhttp.mockwebserver.MockWebServer$3 
processOneRequest
INFO: MockWebServer[60070] received request: DELETE 
/v1.15/containers/6d35806c1bd2b25cd92bba2d2c2c5169dc2156f53ab45c2b62d76e2d2fee14a9
 HTTP/1.1 and responded: HTTP/1.1 204 OK
Jan 24, 2015 3:05:52 PM com.squareup.okhttp.mockwebserver.MockWebServer$2 
acceptConnections
INFO: MockWebServer[49446] done accepting connections: Socket closed
Jan 24, 2015 3:05:52 PM com.squareup.okhttp.mockwebserver.MockWebServer$2 
acceptConnections
INFO: MockWebServer[46039] done accepting connections: Socket closed
Jan 24, 2015 3:05:52 PM com.squareup.okhttp.mockwebserver.MockWebServer$2 
acceptConnections
INFO: MockWebServer[60070] done accepting connections: Socket closed
[pool-13-thread-1] Test 
testRemoveContainer(org.jclouds.docker.features.ContainerApiMockTest) 
succeeded: 799ms
Test suite progress: tests succeeded: 28, failed: 0, skipped: 0.
Jan 24, 2015 3:05:52 PM com.squareup.okhttp.mockwebserver.MockWebServer$3 
processOneRequest
INFO: MockWebServer[46039] received request: POST /v1.15/containers/1/stop 
HTTP/1.1 and responded: HTTP/1.1 200 OK
Starting test 
testWaitContainer(org.jclouds.docker.features.ContainerApiMockTest)
[pool-13-thread-5] Test 
testStopContainer(org.jclouds.docker.features.ContainerApiMockTest) succeeded: 
769ms
Test suite progress: tests succeeded: 29, failed: 0, skipped: 0.
Jan 24, 2015 3:05:52 PM com.squareup.okhttp.mockwebserver

Jenkins build is back to normal : jclouds-labs-openstack #609

2015-01-24 Thread jenkins-no-reply
See 



[jira] [Updated] (JCLOUDS-96) address aws-s3 live test failures

2015-01-24 Thread Andrew Gaul (JIRA)

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

Andrew Gaul updated JCLOUDS-96:
---
Description: 
This should not block the 1.6.1 release but we should address these:

{noformat}
Failed tests:   
testCopyIfModifiedSince(org.jclouds.aws.s3.AWSS3ClientLiveTest): request PUT 
https://gaul-blobstore8.s3.amazonaws.com/pears HTTP/1.1 failed with code 412, 
error: AWSError{requestId='2C3067DD0F517071', 
requestToken='BCYXQkcYsJn5a4ICR+sfMg0DDkfG3nJSESzGlZv1xjbW6yb/1ohcCNHHQYY7A3VJ',
 code='PreconditionFailed', message='At least one of the pre-conditions you 
specified did not hold', 
context='{Condition=x-amz-copy-source-If-Modified-Since, 
HostId=BCYXQkcYsJn5a4ICR+sfMg0DDkfG3nJSESzGlZv1xjbW6yb/1ohcCNHHQYY7A3VJ}'}
  
testDirectory(org.jclouds.aws.s3.blobstore.integration.AWSS3ContainerIntegrationLiveTest):
 [[type=RELATIVE_PATH, id=null, name=directory, location={scope=REGION, 
id=us-standard, description=us-standard, parent=aws-s3, iso3166Codes=[US]}, 
uri=https://gaul-blobstore18.s3.amazonaws.com/directory/, userMetadata={}]]
  
testPutFileParallel(org.jclouds.aws.s3.blobstore.integration.AWSS3BlobIntegrationLiveTest):
 putFileParallel, completed: 0/10, errors: 0, rate: 3000ms/op
  
testPublicAccessInNonDefaultLocation(org.jclouds.aws.s3.blobstore.integration.AWSS3ContainerLiveTest):
 Validation on 'public abstract 
com.google.common.util.concurrent.ListenableFuture 
org.jclouds.s3.S3AsyncClient.putBucketInRegion(java.lang.String,java.lang.String,org.jclouds.s3.options.PutBucketOptions[])[us-standard,
 
gaul-blobstore166105864973802436317-88465623902772003-29211719058811089442391555942423291658,
 [Lorg.jclouds.s3.options.PutBucketOptions;@6954bfe]' didn't pass:(..)
{noformat}

  was:
This should not block the 1.6.1 release but we should address these:

Failed tests:   
testCopyIfModifiedSince(org.jclouds.aws.s3.AWSS3ClientLiveTest): request PUT 
https://gaul-blobstore8.s3.amazonaws.com/pears HTTP/1.1 failed with code 412, 
error: AWSError{requestId='2C3067DD0F517071', 
requestToken='BCYXQkcYsJn5a4ICR+sfMg0DDkfG3nJSESzGlZv1xjbW6yb/1ohcCNHHQYY7A3VJ',
 code='PreconditionFailed', message='At least one of the pre-conditions you 
specified did not hold', 
context='{Condition=x-amz-copy-source-If-Modified-Since, 
HostId=BCYXQkcYsJn5a4ICR+sfMg0DDkfG3nJSESzGlZv1xjbW6yb/1ohcCNHHQYY7A3VJ}'}
  
testDirectory(org.jclouds.aws.s3.blobstore.integration.AWSS3ContainerIntegrationLiveTest):
 [[type=RELATIVE_PATH, id=null, name=directory, location={scope=REGION, 
id=us-standard, description=us-standard, parent=aws-s3, iso3166Codes=[US]}, 
uri=https://gaul-blobstore18.s3.amazonaws.com/directory/, userMetadata={}]]
  
testPutFileParallel(org.jclouds.aws.s3.blobstore.integration.AWSS3BlobIntegrationLiveTest):
 putFileParallel, completed: 0/10, errors: 0, rate: 3000ms/op
  
testPublicAccessInNonDefaultLocation(org.jclouds.aws.s3.blobstore.integration.AWSS3ContainerLiveTest):
 Validation on 'public abstract 
com.google.common.util.concurrent.ListenableFuture 
org.jclouds.s3.S3AsyncClient.putBucketInRegion(java.lang.String,java.lang.String,org.jclouds.s3.options.PutBucketOptions[])[us-standard,
 
gaul-blobstore166105864973802436317-88465623902772003-29211719058811089442391555942423291658,
 [Lorg.jclouds.s3.options.PutBucketOptions;@6954bfe]' didn't pass:(..)


> address aws-s3 live test failures
> -
>
> Key: JCLOUDS-96
> URL: https://issues.apache.org/jira/browse/JCLOUDS-96
> Project: jclouds
>  Issue Type: Bug
>  Components: jclouds-blobstore
>Affects Versions: 1.6.0
>Reporter: Andrew Gaul
>Assignee: Andrew Gaul
>  Labels: aws-s3
> Fix For: 1.9.0
>
>
> This should not block the 1.6.1 release but we should address these:
> {noformat}
> Failed tests:   
> testCopyIfModifiedSince(org.jclouds.aws.s3.AWSS3ClientLiveTest): request PUT 
> https://gaul-blobstore8.s3.amazonaws.com/pears HTTP/1.1 failed with code 412, 
> error: AWSError{requestId='2C3067DD0F517071', 
> requestToken='BCYXQkcYsJn5a4ICR+sfMg0DDkfG3nJSESzGlZv1xjbW6yb/1ohcCNHHQYY7A3VJ',
>  code='PreconditionFailed', message='At least one of the pre-conditions you 
> specified did not hold', 
> context='{Condition=x-amz-copy-source-If-Modified-Since, 
> HostId=BCYXQkcYsJn5a4ICR+sfMg0DDkfG3nJSESzGlZv1xjbW6yb/1ohcCNHHQYY7A3VJ}'}
>   
> testDirectory(org.jclouds.aws.s3.blobstore.integration.AWSS3ContainerIntegrationLiveTest):
>  [[type=RELATIVE_PATH, id=null, name=directory, location={scope=REGION, 
> id=us-standard, description=us-standard, parent=aws-s3, iso3166Codes=[US]}, 
> uri=https://gaul-blobstore18.s3.amazonaws.com/directory/, userMetadata={}]]
>   
> testPutFileParallel(org.jclouds.aws.s3.blobstore.integration.AWSS3BlobIntegrationLiveTest):
>  putFileParallel, completed: 0/10, errors: 0, rate: 3000ms/op
>   
> testPublicAccess

[jira] [Updated] (JCLOUDS-461) aws-s3 live tests have many bucket does not exist failures

2015-01-24 Thread Andrew Gaul (JIRA)

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

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

  was:
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.


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

[jira] [Resolved] (JCLOUDS-96) address aws-s3 live test failures

2015-01-24 Thread Andrew Gaul (JIRA)

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

Andrew Gaul resolved JCLOUDS-96.

Resolution: Fixed

> address aws-s3 live test failures
> -
>
> Key: JCLOUDS-96
> URL: https://issues.apache.org/jira/browse/JCLOUDS-96
> Project: jclouds
>  Issue Type: Bug
>  Components: jclouds-blobstore
>Affects Versions: 1.6.0
>Reporter: Andrew Gaul
>Assignee: Andrew Gaul
>  Labels: aws-s3
> Fix For: 1.9.0
>
>
> This should not block the 1.6.1 release but we should address these:
> {noformat}
> Failed tests:   
> testCopyIfModifiedSince(org.jclouds.aws.s3.AWSS3ClientLiveTest): request PUT 
> https://gaul-blobstore8.s3.amazonaws.com/pears HTTP/1.1 failed with code 412, 
> error: AWSError{requestId='2C3067DD0F517071', 
> requestToken='BCYXQkcYsJn5a4ICR+sfMg0DDkfG3nJSESzGlZv1xjbW6yb/1ohcCNHHQYY7A3VJ',
>  code='PreconditionFailed', message='At least one of the pre-conditions you 
> specified did not hold', 
> context='{Condition=x-amz-copy-source-If-Modified-Since, 
> HostId=BCYXQkcYsJn5a4ICR+sfMg0DDkfG3nJSESzGlZv1xjbW6yb/1ohcCNHHQYY7A3VJ}'}
>   
> testDirectory(org.jclouds.aws.s3.blobstore.integration.AWSS3ContainerIntegrationLiveTest):
>  [[type=RELATIVE_PATH, id=null, name=directory, location={scope=REGION, 
> id=us-standard, description=us-standard, parent=aws-s3, iso3166Codes=[US]}, 
> uri=https://gaul-blobstore18.s3.amazonaws.com/directory/, userMetadata={}]]
>   
> testPutFileParallel(org.jclouds.aws.s3.blobstore.integration.AWSS3BlobIntegrationLiveTest):
>  putFileParallel, completed: 0/10, errors: 0, rate: 3000ms/op
>   
> testPublicAccessInNonDefaultLocation(org.jclouds.aws.s3.blobstore.integration.AWSS3ContainerLiveTest):
>  Validation on 'public abstract 
> com.google.common.util.concurrent.ListenableFuture 
> org.jclouds.s3.S3AsyncClient.putBucketInRegion(java.lang.String,java.lang.String,org.jclouds.s3.options.PutBucketOptions[])[us-standard,
>  
> gaul-blobstore166105864973802436317-88465623902772003-29211719058811089442391555942423291658,
>  [Lorg.jclouds.s3.options.PutBucketOptions;@6954bfe]' didn't pass:(..)
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Resolved] (JCLOUDS-351) testCopyIfModifiedSince fails against AWS-S3

2015-01-24 Thread Andrew Gaul (JIRA)

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

Andrew Gaul resolved JCLOUDS-351.
-
Resolution: Fixed
  Assignee: Andrew Gaul

> testCopyIfModifiedSince fails against AWS-S3
> 
>
> Key: JCLOUDS-351
> URL: https://issues.apache.org/jira/browse/JCLOUDS-351
> Project: jclouds
>  Issue Type: Bug
>  Components: jclouds-blobstore
>Affects Versions: 1.6.3
>Reporter: Andrew Gaul
>Assignee: Andrew Gaul
>  Labels: aws-s3
> Fix For: 1.9.0
>
>
> {noformat}
> testCopyIfModifiedSince(org.jclouds.aws.s3.AWSS3ClientLiveTest)  Time 
> elapsed: 2.929 sec  <<< FAILURE!
> org.jclouds.aws.AWSResponseException: request PUT 
> https://gaul-blobstore1330667931334611482.s3.amazonaws.com/pears HTTP/1.1 
> failed with code 412, error: AWSError{requestId='...', requestToken='...', 
> code='PreconditionFailed', message='At least one of the pre-conditions you 
> specified did not hold', 
> context='{Condition=x-amz-copy-source-If-Modified-Since, HostId=...}'}
> at 
> org.jclouds.aws.handlers.ParseAWSErrorFromXmlContent.handleError(ParseAWSErrorFromXmlContent.java:76)
> at 
> org.jclouds.http.handlers.DelegatingErrorHandler.handleError(DelegatingErrorHandler.java:67)
> at 
> org.jclouds.http.internal.BaseHttpCommandExecutorService.shouldContinue(BaseHttpCommandExecutorService.java:180)
> at 
> org.jclouds.http.internal.BaseHttpCommandExecutorService.invoke(BaseHttpCommandExecutorService.java:150)
> at 
> org.jclouds.rest.internal.InvokeSyncToAsyncHttpMethod.invoke(InvokeSyncToAsyncHttpMethod.java:131)
> at 
> org.jclouds.rest.internal.InvokeSyncToAsyncHttpMethod.apply(InvokeSyncToAsyncHttpMethod.java:97)
> at 
> org.jclouds.rest.internal.InvokeSyncToAsyncHttpMethod.apply(InvokeSyncToAsyncHttpMethod.java:58)
> at 
> org.jclouds.rest.internal.DelegatesToInvocationFunction.handle(DelegatesToInvocationFunction.java:157)
> at 
> org.jclouds.rest.internal.DelegatesToInvocationFunction.invoke(DelegatesToInvocationFunction.java:124)
> at com.sun.proxy.$Proxy56.copyObject(Unknown Source)
> at 
> org.jclouds.s3.S3ClientLiveTest.testCopyIfModifiedSince(S3ClientLiveTest.java:374)
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (JCLOUDS-805) Google Cloud Storage integration test failures

2015-01-24 Thread Andrew Gaul (JIRA)

[ 
https://issues.apache.org/jira/browse/JCLOUDS-805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14290841#comment-14290841
 ] 

Andrew Gaul commented on JCLOUDS-805:
-

[~Bhash90] I actually see more failures and skipped tests with that commit:

{noformat}
Failed tests:
  
GoogleCloudStorageBlobIntegrationLiveTest>BaseBlobIntegrationTest.testPutMultipartInputStream:555->BaseBlobIntegrationTest.testPut:575
 » HttpResponse
  
GoogleCloudStorageContainerIntegrationLiveTest>BaseContainerIntegrationTest.testDelimiter:331
Expected size:<3> but was:<5> in:
<[[type=BLOB, id=gaul-blobstore1442835205159238534/asdf/1422101966696000, 
name=asdf, location=null, 
uri=https://www.googleapis.com/storage/v1/b/gaul-blobstore1442835205159238534/o/asdf,
 userMetadata={}], [type=BLOB, 
id=gaul-blobstore1442835205159238534/boo/bar/1422101967248000, name=boo/bar, 
location=null, 
uri=https://www.googleapis.com/storage/v1/b/gaul-blobstore1442835205159238534/o/boo%2Fbar,
 userMetadata={}], [type=BLOB, 
id=gaul-blobstore1442835205159238534/boo/baz/xyzzy/142210196762, 
name=boo/baz/xyzzy, location=null, 
uri=https://www.googleapis.com/storage/v1/b/gaul-blobstore1442835205159238534/o/boo%2Fbaz%2Fxyzzy,
 userMetadata={}], [type=BLOB, 
id=gaul-blobstore1442835205159238534/cquux/bla/1422101968508000, 
name=cquux/bla, location=null, 
uri=https://www.googleapis.com/storage/v1/b/gaul-blobstore1442835205159238534/o/cquux%2Fbla,
 userMetadata={}], [type=BLOB, 
id=gaul-blobstore1442835205159238534/cquux/thud/1422101968126000, 
name=cquux/thud, location=null, 
uri=https://www.googleapis.com/storage/v1/b/gaul-blobstore1442835205159238534/o/cquux%2Fthud,
 userMetadata={}]]>
  BucketAccessControlsApiLiveTest.testCreateBucketAcl:49->createBucket:43 » 
NullPointer
  BucketApiLiveTest.testCreateBucket:69 » NullPointer param{project} for 
invocat...
  BucketApiLiveTest.testCreateBucketWithOptions:119 » NullPointer 
param{project}...
  
DefaultObjectAccessControlsApiLiveTest.testCreateDefaultObjectAcl:49->createBucket:43
 » NullPointer
  
GoogleCloudStorageBlobIntegrationLiveTest.testMultipartChunkedFileStream:234->addMultipartBlobToContainer:252
 » HttpResponse
  GoogleCloudStorageBlobLiveTest.testCopyUrl:63 » NullPointer httpStreamUrl
  ObjectApiLiveTest.createBucket:93 » NullPointer param{project} for invocation 
...

Tests run: 109, Failures: 9, Errors: 0, Skipped: 55
{noformat}

> Google Cloud Storage integration test failures
> --
>
> Key: JCLOUDS-805
> URL: https://issues.apache.org/jira/browse/JCLOUDS-805
> Project: jclouds
>  Issue Type: Bug
>  Components: jclouds-blobstore
>Affects Versions: 1.9.0
>Reporter: Andrew Gaul
>Assignee: Bhathiya Supun
>  Labels: google-cloud-storage
> Fix For: 1.9.0
>
> Attachments: testresults.txt
>
>
> {noformat}
> Failed tests:
>   
> GoogleCloudStorageBlobIntegrationLiveTest>BaseBlobIntegrationTest.testPutByteSource:531->BaseBlobIntegrationTest.testPut:574
>  » HttpResponse
>   
> GoogleCloudStorageBlobIntegrationLiveTest>BaseBlobIntegrationTest.testPutIncorrectContentMD5:277
>  null
>   
> GoogleCloudStorageBlobIntegrationLiveTest>BaseBlobIntegrationTest.testPutInputStream:539->BaseBlobIntegrationTest.testPut:574
>  » HttpResponse
>   
> GoogleCloudStorageContainerIntegrationLiveTest>BaseContainerIntegrationTest.deleteContainerIfEmptyWithoutContents:372
>  » ResourceNotFound
>   
> GoogleCloudStorageContainerIntegrationLiveTest>BaseContainerIntegrationTest.testListContainerGetBlobSize:409
>  expected [42] but found [null]
>   
> GoogleCloudStorageContainerIntegrationLiveTest>BaseContainerIntegrationTest.testListMarkerAfterLastKey:88
>  » HttpResponse
>   ResumableUploadApiLiveTest.testResumableChunkedUpload:120 expected object 
> to not be null
>   ResumableUploadApiLiveTest.testResumableJpegUpload:83 expected object to 
> not be null
>   BucketApiLiveTest.testPatchBucket:192 » Authorization {
>  "error": {
>   "errors"...
>   BucketApiLiveTest.testUpdateBucket:133 » Authorization {
>  "error": {
>   "errors...
>   BucketApiLiveTest.testUpdateBucketWithOptions:146 » Authorization {
>  "error": ...
>   ObjectApiLiveTest.testSimpleJpegUpload:157->checkHashCodes:399 expected 
> [8FdApr35Ql5P3B1cOAavYg==] but found [f05740a6bdf9425e4fdc1d5c3806af62]
>   ObjectApiLiveTest.testUpdateObject:293 » Authorization {
>  "error": {
>   "errors...
>   ObjectApiLiveTest.deleteBucket:425 » IllegalState {
>  "error": {
>   "errors": [
> ...
> Tests run: 100, Failures: 14, Errors: 0, Skipped: 17
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


Jenkins build is back to normal : jclouds-labs #745

2015-01-24 Thread jenkins-no-reply
See 



Jenkins build is back to normal : jclouds-labs » jclouds docker API #745

2015-01-24 Thread jenkins-no-reply
See 




Jenkins build is back to normal : jclouds-karaf #878

2015-01-24 Thread jenkins-no-reply
See 



Build failed in Jenkins: jclouds » jclouds jsch ssh client #2917

2015-01-24 Thread jenkins-no-reply
See 


--
[...truncated 4 lines...]
[INFO] 
[INFO] 
[INFO] Building jclouds jsch ssh client 2.0.0-SNAPSHOT
[INFO] 
Downloading: 
http://repo.cloudbees.com/content/repositories/central/com/jcraft/jsch/0.1.49/jsch-0.1.49.pom
Downloaded: 
http://repo.cloudbees.com/content/repositories/central/com/jcraft/jsch/0.1.49/jsch-0.1.49.pom
 (4 KB at 185.8 KB/sec)
Downloading: 
http://repo.cloudbees.com/content/repositories/central/com/jcraft/jsch.agentproxy.jsch/0.0.8/jsch.agentproxy.jsch-0.0.8.pom
Downloaded: 
http://repo.cloudbees.com/content/repositories/central/com/jcraft/jsch.agentproxy.jsch/0.0.8/jsch.agentproxy.jsch-0.0.8.pom
 (2 KB at 82.7 KB/sec)
Downloading: 
http://repo.cloudbees.com/content/repositories/central/com/jcraft/jsch/0.1.49/jsch-0.1.49.jar
Downloading: 
http://repo.cloudbees.com/content/repositories/central/com/jcraft/jsch.agentproxy.jsch/0.0.8/jsch.agentproxy.jsch-0.0.8.jar
Downloaded: 
http://repo.cloudbees.com/content/repositories/central/com/jcraft/jsch.agentproxy.jsch/0.0.8/jsch.agentproxy.jsch-0.0.8.jar
 (5 KB at 304.9 KB/sec)
Downloaded: 
http://repo.cloudbees.com/content/repositories/central/com/jcraft/jsch/0.1.49/jsch-0.1.49.jar
 (224 KB at 11185.8 KB/sec)
[INFO] 
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ jclouds-jsch ---
[INFO] 
[INFO] --- maven-enforcer-plugin:1.1.1:enforce (enforce-banned-dependencies) @ 
jclouds-jsch ---
[INFO] 
[INFO] --- maven-enforcer-plugin:1.1.1:enforce (enforce-java) @ jclouds-jsch ---
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (default) @ jclouds-jsch 
---
[INFO] 
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ 
jclouds-jsch ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] skip non existing resourceDirectory 

[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ jclouds-jsch 
---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 3 source files to 

[WARNING] bootstrap class path not set in conjunction with -source 1.6
[WARNING] 
:
 

 uses or overrides a deprecated API.
[WARNING] 
:
 Recompile with -Xlint:deprecation for details.
[INFO] 
[INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ 
jclouds-jsch ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ 
jclouds-jsch ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 3 source files to 

[WARNING] bootstrap class path not set in conjunction with -source 1.6
[WARNING] Cannot find annotation method 'value()' in type 
'com.google.auto.service.AutoService': class file for 
com.google.auto.service.AutoService not found
[INFO] 
[INFO] --- maven-surefire-plugin:2.17:test (default-test) @ jclouds-jsch ---
[INFO] Surefire report directory: 


---
 T E S T S
---
Running TestSuite
Configuring TestNG with: TestNG652Configurator
Starting test testExceptionMessagesRetry(org.jclouds.ssh.jsch.JschSshClientTest)
Starting test 
testConfigureBindsClient(org.jclo

Build failed in Jenkins: jclouds #2917

2015-01-24 Thread jenkins-no-reply
See 

Changes:

[Andrew Gaul] Skip tests which cannot run on Atmos

--
[...truncated 38105 lines...]
[JENKINS] Archiving 
 to 
org.apache.jclouds.api/sqs/2.0.0-SNAPSHOT/sqs-2.0.0-SNAPSHOT.pom
[JENKINS] Archiving 

 to 
org.apache.jclouds.api/sqs/2.0.0-20150124.231926-169/sqs-2.0.0-20150124.231926-169.jar
[JENKINS] Archiving 

 to 
org.apache.jclouds.api/sqs/2.0.0-20150124.231926-169/sqs-2.0.0-20150124.231926-169-tests.jar
[JENKINS] Archiving 
 to 
org.apache.jclouds.api/swift/2.0.0-SNAPSHOT/swift-2.0.0-SNAPSHOT.pom
[JENKINS] Archiving 

 to 
org.apache.jclouds.api/swift/2.0.0-20150124.232216-166/swift-2.0.0-20150124.232216-166.jar
[JENKINS] Archiving 

 to 
org.apache.jclouds.api/swift/2.0.0-20150124.232216-166/swift-2.0.0-20150124.232216-166-tests.jar
[JENKINS] Archiving 
 to 
org.apache.jclouds.api/filesystem/2.0.0-SNAPSHOT/filesystem-2.0.0-SNAPSHOT.pom
[JENKINS] Archiving 

 to 
org.apache.jclouds.api/filesystem/2.0.0-20150124.231609-176/filesystem-2.0.0-20150124.231609-176.jar
[JENKINS] Archiving 

 to 
org.apache.jclouds.api/filesystem/2.0.0-20150124.231609-176/filesystem-2.0.0-20150124.231609-176-tests.jar
[JENKINS] Archiving 
 
to 
org.apache.jclouds.provider/azureblob/2.0.0-SNAPSHOT/azureblob-2.0.0-SNAPSHOT.pom
[JENKINS] Archiving 

 to 
org.apache.jclouds.provider/azureblob/2.0.0-20150124.233515-163/azureblob-2.0.0-20150124.233515-163.jar
[JENKINS] Archiving 

 to 
org.apache.jclouds.provider/azureblob/2.0.0-20150124.233515-163/azureblob-2.0.0-20150124.233515-163-tests.jar
[JENKINS] Archiving 

 to 
org.apache.jclouds.provider/elastichosts-lon-p/2.0.0-SNAPSHOT/elastichosts-lon-p-2.0.0-SNAPSHOT.pom
[JENKINS] Archiving 

 to 
org.apache.jclouds.provider/elastichosts-lon-p/2.0.0-20150124.233941-163/elastichosts-lon-p-2.0.0-20150124.233941-163.jar
[JENKINS] Archiving 

 to 
org.apache.jclouds.provider/elastichosts-lon-p/2.0.0-20150124.233941-163/elastichosts-lon-p-2.0.0-20150124.233941-163-tests.jar
[JENKINS] Archiving 

 to 
org.apache.jclouds.provider/cloudfiles-us/2.0.0-SNAPSHOT/cloudfiles-us-2.0.0-SNAPSHOT.pom
[JENKINS] Archiving 

 to 
org.apache.jclouds.provider/cloudfiles-us/2.0.0-20150124.234653-163/cloudfiles-us-2.0.0-20150124.234653-163.jar
[JENKINS] Archiving 

 to 
org.apache.jclouds.provider/cloudfiles-us/2.0.0-20150124.234653-163/cloudfiles-us-2.0.0-20150124.234653-163-tests.jar
[JENKINS] Archiving 
 to 
org.apache.jclouds.driver/jclouds-sshj/2.0.0-SNAPSHOT/jclouds-sshj-2.0.0-SNAPSHOT.pom
[JENKINS] Archiving 

 to 
org.apache.jclouds.driver/jclouds-sshj/2.0.0-20150124.231253-179/jclouds-sshj-2.0.0-20150124.231253-179.jar
[JENKINS] Archiving 

 to 
org.apache.jclouds.driver/jclouds-sshj/2.0.0-20150124.231253-179/jclouds-sshj-2.0.0-20150124.231253-179-tests.jar
[JENKINS] Archiving 

 to 
org.apache.jclouds.provider/elastichosts-sjc-c/2.

Jenkins build is back to normal : jclouds #2918

2015-01-24 Thread jenkins-no-reply
See 



Jenkins build is back to normal : jclouds » jclouds jsch ssh client #2918

2015-01-24 Thread jenkins-no-reply
See 




[jira] [Closed] (JCLOUDS-407) JClouds (HPCloud) documentation is not upto date

2015-01-24 Thread Chris Custine (JIRA)

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

Chris Custine closed JCLOUDS-407.
-
   Resolution: Fixed
Fix Version/s: 1.8.0
 Assignee: Chris Custine

I'm closing this because the HP Cloud documentation was updated for 1.8.0 and 
is still current.  I didn't notice this older issue about docs at the time.

> JClouds (HPCloud) documentation is not upto date
> 
>
> Key: JCLOUDS-407
> URL: https://issues.apache.org/jira/browse/JCLOUDS-407
> Project: jclouds
>  Issue Type: Improvement
>  Components: docs
>Affects Versions: 1.6.2
>Reporter: uma maheswari mohandoss
>Assignee: Chris Custine
> Fix For: 1.8.0
>
>
> The documentation needs an update according to the latest jclouds version. It 
> would seem that a new user who just followed instructions on JClouds website 
> and tried to run simplest example they have would fail miserably to achieve 
> anything.  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Closed] (JCLOUDS-408) JClouds(HPCloud): Server list fails with JSON error.

2015-01-24 Thread Chris Custine (JIRA)

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

Chris Custine closed JCLOUDS-408.
-
   Resolution: Fixed
Fix Version/s: 1.8.0
 Assignee: Chris Custine

This was fixed in 1.8.0.

> JClouds(HPCloud): Server list fails with JSON error.
> 
>
> Key: JCLOUDS-408
> URL: https://issues.apache.org/jira/browse/JCLOUDS-408
> Project: jclouds
>  Issue Type: Bug
>  Components: jclouds-compute
>Affects Versions: 1.6.2
>Reporter: uma maheswari mohandoss
>Assignee: Chris Custine
>  Labels: hpcloud-compute
> Fix For: 1.8.0
>
>
> JClouds - HPCloud.
> JClouds version tried:  1.6.1, 16.2, 1.6.2-incubating.
> List server fails when there is a VM booted from volume.
> Consider VM that is booted from volume, this VM is then listed by fetching 
> list from servers/details - such server has no image. However in JSON 
> response image is returned as empty string.  Finally resulting in JSON error.
> Note:  If server list DOES NOT contain VM booted from volume, NOT hitting 
> this issue.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


Re: [jclouds-site] Update blobstore.md (#151)

2015-01-24 Thread jclouds-commentator
 to review your changes.

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/151#issuecomment-71350822

[jclouds-site] Update blobstore.md (#151)

2015-01-24 Thread Xianheng Ma
simple fix for 404 broken link.
You can view, comment on, or merge this pull request online at:

  https://github.com/jclouds/jclouds-site/pull/151

-- Commit Summary --

  * Update blobstore.md

-- File Changes --

M start/blobstore.md (3)

-- Patch Links --

https://github.com/jclouds/jclouds-site/pull/151.patch
https://github.com/jclouds/jclouds-site/pull/151.diff

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/151


Re: [jclouds-site] Update blobstore.md (#151)

2015-01-24 Thread Xianheng Ma
I was just browsing this page (http://jclouds.apache.org/start/blobstore/) and 
see the link for testUploadBigFile is broken. 

simply fix it.

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/151#issuecomment-71350853

[jira] [Commented] (JCLOUDS-805) Google Cloud Storage integration test failures

2015-01-24 Thread Bhathiya Supun (JIRA)

[ 
https://issues.apache.org/jira/browse/JCLOUDS-805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14290990#comment-14290990
 ] 

Bhathiya Supun commented on JCLOUDS-805:


[~gaul] I changed ~/.m2/settings.xml to  add
YOUR-PROJECT-NUMBER

My setting.xml is ass follows


1234567891234-abcede567...@developer.gserviceaccount.com

-BEGIN RSA PRIVATE KEY-
IMP+fAo74Yfr1LgIdb5eRJzjO816nYxP6x/sEP3UQAB6S2GEa94JOqjZvAxPfAEMaaNv126AFIk/9wSOYHW
fXsMYjfcLxKUCT62t8sCQQCo+sL5+V6BV0LWJCv7onGwUlnxXdbkXBHDOHo8/rbr
BgW/bJbMLidIwtGQ27duziVbtoMHpvfaAlWAjOF4Irt/
-END RSA PRIVATE KEY-
12345678


I'd edit the GCS README  file

> Google Cloud Storage integration test failures
> --
>
> Key: JCLOUDS-805
> URL: https://issues.apache.org/jira/browse/JCLOUDS-805
> Project: jclouds
>  Issue Type: Bug
>  Components: jclouds-blobstore
>Affects Versions: 1.9.0
>Reporter: Andrew Gaul
>Assignee: Bhathiya Supun
>  Labels: google-cloud-storage
> Fix For: 1.9.0
>
> Attachments: testresults.txt
>
>
> {noformat}
> Failed tests:
>   
> GoogleCloudStorageBlobIntegrationLiveTest>BaseBlobIntegrationTest.testPutByteSource:531->BaseBlobIntegrationTest.testPut:574
>  » HttpResponse
>   
> GoogleCloudStorageBlobIntegrationLiveTest>BaseBlobIntegrationTest.testPutIncorrectContentMD5:277
>  null
>   
> GoogleCloudStorageBlobIntegrationLiveTest>BaseBlobIntegrationTest.testPutInputStream:539->BaseBlobIntegrationTest.testPut:574
>  » HttpResponse
>   
> GoogleCloudStorageContainerIntegrationLiveTest>BaseContainerIntegrationTest.deleteContainerIfEmptyWithoutContents:372
>  » ResourceNotFound
>   
> GoogleCloudStorageContainerIntegrationLiveTest>BaseContainerIntegrationTest.testListContainerGetBlobSize:409
>  expected [42] but found [null]
>   
> GoogleCloudStorageContainerIntegrationLiveTest>BaseContainerIntegrationTest.testListMarkerAfterLastKey:88
>  » HttpResponse
>   ResumableUploadApiLiveTest.testResumableChunkedUpload:120 expected object 
> to not be null
>   ResumableUploadApiLiveTest.testResumableJpegUpload:83 expected object to 
> not be null
>   BucketApiLiveTest.testPatchBucket:192 » Authorization {
>  "error": {
>   "errors"...
>   BucketApiLiveTest.testUpdateBucket:133 » Authorization {
>  "error": {
>   "errors...
>   BucketApiLiveTest.testUpdateBucketWithOptions:146 » Authorization {
>  "error": ...
>   ObjectApiLiveTest.testSimpleJpegUpload:157->checkHashCodes:399 expected 
> [8FdApr35Ql5P3B1cOAavYg==] but found [f05740a6bdf9425e4fdc1d5c3806af62]
>   ObjectApiLiveTest.testUpdateObject:293 » Authorization {
>  "error": {
>   "errors...
>   ObjectApiLiveTest.deleteBucket:425 » IllegalState {
>  "error": {
>   "errors": [
> ...
> Tests run: 100, Failures: 14, Errors: 0, Skipped: 17
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)