Re: [DISCUSS] Release Apache jclouds 2.2.1 RC1

2020-05-13 Thread Andrew Phillips 

[moving this here from the VOTE thread...]

Sorry, I have little expertise with gpg.  I believe this is the same 
key

I have used since 2017.  Does this mean that my key is not signed by
anyone in a chain of trust?  This should not block the release, right?


I don't think this is a release blocker, no - the key is the one listed 
in the KEYS file, which I think is what we're checking for. Just wanted 
to mention it as a heads-up.


Regards

ap

Re: [DISCUSS] Release Apache jclouds 2.2.1 RC1

2020-05-08 Thread Andrew Gaul 
I checked the following resources and we need three +1 from the PMC:

https://projects.apache.org/committee.html?jclouds
https://www.apache.org/foundation/voting.html

Unfortunately JB is committer and thus we lack quorum to close the vote.

On Wed, May 06, 2020 at 09:43:37AM -0400, Andrew Phillips wrote:
> Hi JB
> 
> Just as a matter of procedure, I think your vote may technically be
> "non-binding" rather than "binding"?
> 
> If you were able to run the verification script successfully (I'm still
> wrestling with my local system), I'd be happy to take that information into
> account in my upcoming vote.
> 
> Thanks for taking the time to test the release!
> 
> ap

-- 
Andrew Gaul
http://gaul.org/

Re: [DISCUSS] Release Apache jclouds 2.2.1 RC1

2020-05-06 Thread Andrew Phillips 

Hi JB

Just as a matter of procedure, I think your vote may technically be 
"non-binding" rather than "binding"?


If you were able to run the verification script successfully (I'm still 
wrestling with my local system), I'd be happy to take that information 
into account in my upcoming vote.


Thanks for taking the time to test the release!

ap

Re: [DISCUSS] Release Apache jclouds 2.2.1 RC1

2020-05-05 Thread Andrew Gaul 
On Sat, May 02, 2020 at 07:34:22PM +0900, Andrew Gaul wrote:
> This thread is for discussion of the first release candidate for
> Apache jclouds 2.2.1.
> 
> Please use this thread for discussion of issues uncovered in the RC,
> questions you may have about the RC, etc.
> 
> If you want to help to validate the release, you'll find a set of
> scripts and the corresponding instructions here:
> https://cwiki.apache.org/confluence/display/JCLOUDS/Validate+a+Release
> 
> You can also go run live tests for your preferred providers and post
> the results here, or use the projects in the jclouds-examples repo,
> such as the "compute-basics" to rapidly smoke test the providers you   
> are interested in:
> https://github.com/jclouds/jclouds-examples

Successfully ran blobstore integration tests with similar failures to
2.2.1.  Providers include aws-s3, azureblob, b2, filesystem,
google-cloud-storage, rackspace-cloudfiles-us, s3 (dreamobjects), and
transient.  We can no longer test atmos since Synaptic ended their
service.  Google Cloud Storage has some new failures compared to 2.2.0
despite no changes to the code.

-- 
Andrew Gaul
http://gaul.org/
AWS-S3

Failed tests:
  
PathBasedContainerLiveTest>S3ContainerLiveTest.testPublicAccess:37->BaseContainerLiveTest.testPublicAccess:76
 {name=hello, type=BLOB, uri=https://s3.amazonaws.com/gaul-blobstore5/hello, 
userMetadata={}, eTag="869a42369bf5850326cf30eed63e9b44", lastModified=Mon May 
04 04:21:28 JST 2020, size=46, container=gaul-blobstore5, 
contentMetadata=[cacheControl=null, contentDisposition=null, 
contentEncoding=null, contentLanguage=null, contentLength=46, 
contentMD5=869a42369bf5850326cf30eed63e9b44, contentType=application/unknown, 
expires=null], tier=STANDARD} expected object to not be null
  
AWSS3ContainerLiveTest>S3ContainerLiveTest.testPublicAccess:37->BaseContainerLiveTest.testPublicAccess:76
 {name=hello, type=BLOB, uri=https://gaul-blobstore11.s3.amazonaws.com/hello, 
userMetadata={}, eTag="869a42369bf5850326cf30eed63e9b44", lastModified=Mon May 
04 04:22:00 JST 2020, size=46, container=gaul-blobstore11, 
contentMetadata=[cacheControl=null, contentDisposition=null, 
contentEncoding=null, contentLanguage=null, contentLength=46, 
contentMD5=869a42369bf5850326cf30eed63e9b44, contentType=application/unknown, 
expires=null], tier=STANDARD} expected object to not be null
  AWSS3BlobSignerLiveTest>BaseBlobSignerLiveTest.testSignGetUrlOptions:78 » 
KeyNotFound
  
AWSS3ServiceIntegrationLiveTest>BaseServiceIntegrationTest.testAllLocations:50 
» AWSResponse

Tests run: 164, Failures: 4, Errors: 0, Skipped: 9



AZUREBLOB

Failed tests:
  
AzureBlobIntegrationLiveTest>BaseBlobIntegrationTest.testCopyIfNoneMatchNegative:1151
Expecting:
 <304>
to be equal to:
 <412>
but was not.
  AzureBlobClientLiveTest.testCopyBlobIfModifiedSince:469 » HttpResponse 
command...
  AzureBlobClientLiveTest.testCopyBlobIfNoneMatch:552 » HttpResponse command: 
PU...

Tests run: 140, Failures: 3, Errors: 0, Skipped: 12



BACKBLAZE B2

Tests run: 128, Failures: 0, Errors: 0, Skipped: 28



FILESYSTEM

Tests run: 110, Failures: 0, Errors: 0, Skipped: 10



GOOGLE CLOUD STORAGE

Failed tests:
  
GoogleCloudStorageBlobSignerLiveTest>BaseBlobSignerLiveTest.testSignGetUrl:54->BaseBlobStoreIntegrationTest.getContainerName:453->BaseBlobStoreIntegrationTest.createContainerAndEnsureEmpty:273->BaseBlobStoreIntegrationTest.createContainerAndEnsureEmpty:265
 » IllegalArgument
  
GoogleCloudStorageBlobSignerLiveTest>BaseBlobSignerLiveTest.testSignGetUrlOptions:72->BaseBlobStoreIntegrationTest.getContainerName:453->BaseBlobStoreIntegrationTest.createContainerAndEnsureEmpty:273->BaseBlobStoreIntegrationTest.createContainerAndEnsureEmpty:265
 » IllegalArgument
  
GoogleCloudStorageBlobSignerLiveTest>BaseBlobSignerLiveTest.testSignGetUrlWithTime:90->BaseBlobStoreIntegrationTest.getContainerName:453->BaseBlobStoreIntegrationTest.createContainerAndEnsureEmpty:273->BaseBlobStoreIntegrationTest.createContainerAndEnsureEmpty:265
 » IllegalArgument
  
GoogleCloudStorageBlobSignerLiveTest>BaseBlobSignerLiveTest.testSignGetUrlWithTimeExpired:126->BaseBlobSignerLiveTest.testSignGetUrlWithTime:107->BaseBlobStoreIntegrationTest.getContainerName:453->BaseBlobStoreIntegrationTest.createContainerAndEnsureEmpty:273->BaseBlobStoreIntegrationTest.createContainerAndEnsureEmpty:265
 » IllegalArgument
  
GoogleCloudStorageBlobSignerLiveTest>BaseBlobSignerLiveTest.testSignPutUrl:135->BaseBlobStoreIntegrationTest.getContainerName:453->BaseBlobStoreIntegrationTest.createContainerAndEnsureEmpty:273->BaseBlobStoreIntegrationTest.createContainerAndEnsureEmpty:265
 » IllegalArgument

Re: [DISCUSS] Release Apache jclouds 2.2.1 RC1

2020-05-04 Thread Ignasi Barrera 
Many thanks for cutting the release!
Before formally announcing the release once the vote passes, would you
have time to work on the release notes for the website?

On Sat, May 2, 2020 at 12:34 PM Andrew Gaul  wrote:
>
> This thread is for discussion of the first release candidate for
> Apache jclouds 2.2.1.
>
> Please use this thread for discussion of issues uncovered in the RC,
> questions you may have about the RC, etc.
>
> If you want to help to validate the release, you'll find a set of
> scripts and the corresponding instructions here:
> https://cwiki.apache.org/confluence/display/JCLOUDS/Validate+a+Release
>
> You can also go run live tests for your preferred providers and post
> the results here, or use the projects in the jclouds-examples repo,
> such as the "compute-basics" to rapidly smoke test the providers you
> are interested in:
> https://github.com/jclouds/jclouds-examples
>
> --
> Andrew Gaul
> http://gaul.org/