Some more live tests for the keystone changes:
* openstack-keystone V3: Tests run: 22, Failures: 0, Errors: 0, Skipped: 0
* openstack-keystone V2: Tests run: 30, Failures: 1, Errors: 0, Skipped: 18
The failed test (and the skipped ones) are due to a failure in a
method to list the roles of a user, that seems that no longer existed
in the backend OpenStack Keystone API), so I'd say it is a non-blocker
for the release.
On 19 February 2018 at 16:18, Ignasi Barrera <n...@apache.org> wrote:
> I verified aws-ec2 with the jclouds-examples repo and everything
> worked as expected.
> I also installed the digitalocean2 feature in the jclouds-karaf
> container without issues.
> Live tests executed as part of our weekly CI builds (which build from
> master so we can trust them):
> * chef: Tests run: 66, Failures: 0, Errors: 0, Skipped: 0
> * google-compute-engine: Tests run: 179, Failures: 0, Errors: 0, Skipped: 8
> * packet: Tests run: 53, Failures: 0, Errors: 0, Skipped: 0
> Live tests manually run:
> * digitalocean2: Tests run: 67, Failures: 0, Errors: 0, Skipped: 0
> * azurecompute-arm: Tests run: 223, Failures: 2, Errors: 0, Skipped: 70
> Failed tests:
> VaultApiLiveTest.testCreate:127 » IllegalState
> VaultApiLiveTest.forceVaultRemoval:116 » IllegalArgument
> The failed tests in Azure ARm are due to a couple properties I did not
> pass that are required to run the Vault Live tests. All skipped tests
> are from that class, so there should be nothing problematic here.
> On 18 February 2018 at 23:17, Andrew Gaul <g...@apache.org> wrote:
>> I visually inspected changes from rc2 to rc3 and decided not to run
>> integration tests again. I attached the rc2 results.
>> On Fri, Feb 16, 2018 at 01:14:45PM +0100, Andrea Turli (apache.org) wrote:
>>> This thread is for discussion of the second release candidate for Apache
>>> jclouds 2.1.0.
>>> 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:
>>> 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:
>>> Thank you!
>> Andrew Gaul