Hi! While testing the new Azure ARM security group extension I've found a small issue here [1]. Basically we are not dealing properly the "all protocols" firewall rules, and will always fail to create them.
Given that the SecurityGroupExtension (along with Packet and Vagrant) is one of the important features we're releasing in 2.0.1, I'd like to propose to cancel the RC1 and cut a RC2 with a fix for that. The fix is pretty straightforward, and I'd also have a look at the vagrant feature thing in Karaf (although all tests passed locally for me). WDYT? The change would only affect labs. I don't pretend to be releasing the other unrelated repos again, so I hope to be able to have the RC2 prepared tonight/early tomorrow. Cheers! I. [1] https://github.com/jclouds/jclouds-labs/blob/master/azurecompute-arm/src/main/java/org/jclouds/azurecompute/arm/compute/extensions/AzureComputeSecurityGroupExtension.java#L217 On 19 February 2017 at 20:59, Andrew Gaul <g...@apache.org> wrote: > I attached integration test results against aws-s3, azureblob, b2, > filesystem, glacier, google-cloud-storage, rackspace-cloudfiles-us, s3 > (dreamhost), and transient. > > On Fri, Feb 17, 2017 at 05:05:24PM +0100, Ignasi Barrera wrote: >> This thread is for discussion of the first release candidate for >> Apache jclouds 2.0.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 validating the release, you can follow these >> instructions: >> https://cwiki.apache.org/confluence/display/JCLOUDS/Validate+a+Release >> >> >> Thank you! > > -- > Andrew Gaul > http://gaul.org/
