Hi all, +1 (binding)
Tested the following ... please note PostgreSQL fails on Ubuntu 16 but IMO this is not a blocker for release (ill raise a bug shortly) [✓] Download links work. [✓] Checksums and PGP signatures are valid. [✓] Expanded source archive matches contents of RC tag. [✓] Expanded source archive builds and passes tests. [✓] LICENSE is present and correct. [✓] NOTICE is present and correct, including copyright date. [✓] No compiled archives bundled in source archive. Blueprint Cloud Dist Result --------------------------------------------------------------------------- alfresco OpenStack CentOS 7 pass cassandra OpenStack CentOS 7 pass elk-elasticsearch OpenStack CentOS 7 pass elk-kibana OpenStack CentOS 7 pass elk-logstash OpenStack CentOS 7 pass jenkins OpenStack CentOS 7 pass rethinkdb-node OpenStack CentOS 7 pass squid OpenStack CentOS 7 pass cassandra-fabric OpenStack CentOS 7 pass cassandra-node OpenStack CentOS 7 pass couchdb-node OpenStack CentOS 7 pass couchdb2-node OpenStack CentOS 7 pass elasticsearch OpenStack CentOS 7 pass jboss6 OpenStack CentOS 7 pass jboss7 OpenStack CentOS 7 pass maria-db OpenStack CentOS 7 pass mongo-db OpenStack CentOS 7 pass mysql OpenStack CentOS 7 pass mysql-cluster OpenStack CentOS 7 pass node-js OpenStack CentOS 7 pass postgresql-java OpenStack CentOS 7 pass postgresql-java AWS CentOS 7 pass postgresql-java GCE CentOS 7 pass postgresql-java Softlayer CentOS 7 pass postgresql-java AWS Ubuntu 16 fail postgresql-java Softlayer Ubuntu 16 fail postgresql-java GCE Ubuntu 16 fail postgresql-yaml OpenStack CentOS 7 pass rabbit-mq OpenStack CentOS 7 pass redis OpenStack CentOS 7 pass solr OpenStack CentOS 7 pass tomcat7 OpenStack CentOS 7 pass tomcat8 OpenStack CentOS 7 pass tomcat8 AWS CentOS 7 pass tomcat8 Softlayer CentOS 7 pass tomcat8 GCE CentOS 7 pass tomcat8 Softlayer Ubuntu 16 pass tomcat8 GCE Ubuntu 16 pass tomcat8 AWS Ubuntu 16 pass zookeeper OpenStack CentOS 7 pass zookeeper AWS Ubuntu 16 pass zookeeper AWS CentOS 7 pass zookeeper Softlayer CentOS 7 pass zookeeper Softlayer Ubuntu 16 pass zookeeper GCE CentOS 7 pass zookeeper GCE Ubuntu 16 pass Cheers M On 16 May 2017 at 17:03, Richard Downer <[email protected]> wrote: > Hello all, > > I'm trying out the rc3 and seeing a problem. If I deploy the "Template 3" > app (web server + Riak cluster) from the "New Application" window, then the > individual cluster nodes appear to start, but the cluster as a whole goes > on fire. > > Drilling down, it appears to be a "join cluster" activity which is failing. > The stdout of the task says: > "Node [email protected] is not > reachable!" > > This is running in AWS EC2 in eu-central-1 - everything is in the same > region. > > Can anybody else reproduce? > > Thanks > Richard. > > > On 12 May 2017 at 17:09, Richard Downer <[email protected]> wrote: > > > This thread is for discussions related to the release vote. > > > > I should clarify what we are looking for in a release vote. Particularly, > > we are looking for people to download,validate, and test the release. > > Only if you are satisfied that the artifacts are correct and the quality > is > > high enough, should you make a "+1" vote. Alongside your vote you should > > list > > the checks that you made. > > > > Here is a good example: http://markmail.org/message/gevsz2pdciraw6jw > > > > The vote is not simply about "the master branch contains the features I > > wanted" - > > it is about making sure that *these* artifacts are *correct* (e.g. they > are > > not corrupted, hashes and signatures pass) and are of *sufficiently high > > quality* to be stamped as an official release of The Apache Software > > Foundation. > > > > Why test the artifacts when master is looking good? Here are some > reasons: > > > > - somebody could have made a commit that broke it, since you last git > > pulled > > - the release branch could have been made at the wrong point, or > > inconsistently > > between all of the submodules > > - something in the release process could have broken it > > - I could have made a mistake and corrupted the files > > - a problem with the Apache infrastructure could mean that the release > > files are > > unobtainable or corrupted > > > > This is why the release manager needs you to download the actual release > > artifacts and try them out. > > > > The way Apache works can be a bit arcane sometimes, but it's all done > with > > a reason. If the vote passes then the contents of the email and its links > > become "endorsed" by The Apache Software Foundation, and the Foundation > > will > > take on legal liability for them, forever. > > > > And of course we want the best possible experience for our users - so we > > need > > the actual release files to be tested manually to make sure that a > mistake > > does > > not ruin the experience for users. > > > > So if you can spare an hour or more to download some of the artifacts and > > try > > them out, then it will be *very* useful! The vote lasts for three days so > > there's no need to rush to get a vote in. > > > > Thanks! > > Richard Downer > > >
