+1 I built a DEBUG version of 1.15.0 RC2 from sources on Ubuntu 18.04 and CentOS 8.2 and ran tests for the backend components using ctest.
Ubuntu 18.04: all passed except for: master_authz-itest: AuthzProvidersWithOwner/MasterAuthzOwnerITest.TestMismatchedTable/Ranger_owner CentOS 8.2: all passed except for: master_hms-itest: MasterHmsTest.TestAlterTableOwner, etc. kudu-tool-test: ToolTest.TestHmsIgnoresDifferentMasters (the issue was due to RSA 768bit key -- I'll need to update Ranger's JVM settings to allow for less secure cipher/algorithm constraints). Those Ranger-related tests in master_authz-itest are known to be a bit flaky, it's not a big deal: http://dist-test.cloudera.org:8080/test_drilldown?test_name=master_authz-itest The root case of test failures of the scenarios from master_hms-itest and from kudu-tool-test at CentOS 8.2 is using 768bit RSA key for Kudu IPKI CA in tests -- I'll need to update Ranger's JVM settings to allow for less secure cipher/algorithm constraints. It's a test-only failure related to tighter security settings on contemporary Linux distros, and so not a big deal. The funny fact is that not a single run for my RC verification went without failing at least one of HMS scenarios since HMS tests had been introduced, and I see a similar pattern for this RC :) ToolTest.TestHmsIgnoresDifferentMasters failed because of using 768bit RSA key for Kudu IPKI CA in tests -- I'll need to update Ranger's JVM settings to allow for less secure cipher/algorithm constraints. It's a test-only failure related to tighter security settings on contemporary Linux distros, and so not a big deal. Overall, those test failures are related to test-only defects and known flaky tests, so overall this RC is good to go, IMO. /Alexey On Tue, Jun 15, 2021 at 8:33 PM Bankim Bhavsar <[email protected]> wrote: > Gentle reminder for voting on 1.15.0 RC2. > > -Bankim > > On Thu, Jun 10, 2021 at 3:16 PM Bankim Bhavsar <[email protected]> wrote: > > > Hello Kudu devs! > > > > The Apache Kudu team is happy to announce the second release candidate > for > > Apache Kudu 1.15.0. > > > > Apache Kudu 1.15.0 is a minor release that offers many improvements and > > fixes since Apache Kudu 1.14.0. > > > > This is a source-only release. The artifacts have been staged here: > > https://dist.apache.org/repos/dist/dev/kudu/1.15.0-RC2/ > > > > Branch: branch-1.15.x > > > > Java convenience binaries in the form of a Maven repository are staged > > here: > > https://repository.apache.org/content/repositories/orgapachekudu-1092/ > > > > Linux test-only Kudu binary JAR artifacts are staged here: > > https://repository.apache.org/content/repositories/orgapachekudu-1093/ > > > > MacOS test-only Kudu binary JAR artifacts are staged here: > > https://repository.apache.org/content/repositories/orgapachekudu-1094/ > > > > It is tagged in Git as 1.15.0-RC2 and the corresponding hash is the > > following: > > > > > https://gitbox.apache.org/repos/asf?p=kudu.git;a=commit;h=64619147e7932518bb88b3f3f719d9c27cfdae68 > > > > The Release Notes notes can be found here: > > > https://github.com/apache/kudu/blob/branch-1.15.x/docs/release_notes.adoc > > > > The KEYS file to verify the artifact signatures can be found here: > > https://dist.apache.org/repos/dist/release/kudu/KEYS > > > > Some common release validations include building Kudu, and running the > unit > > tests on your platforms and environments. Additionally it is worth > running > > Kudu Java tests against kudu-binary JAR artifact using > > `-PuseBinJar=<version>` > > as described in the commit message here: > > > > > > > https://gitbox.apache.org/repos/asf?p=kudu.git;a=commit;h=8a6faaa93f3e206ac75e8087731daccaf7ab646a > > > > The vote will run until a majority[1] is achieved, but at least until > > Tuesday > > June 15th 2021, to give everyone a chance to review this release > candidate > > and > > vote. > > > > Thank You, > > Bankim. > > > > [1] https://www.apache.org/foundation/voting.html#ReleaseVotes > > >
