Hi Pat, Sorry for being late with my tests, please find my +1 here:
- verified xsum/sig, - verified cluster with 11 nodes, - verified with few 4lw commands. - all unit test passed locally, - running rolling restart test for a while without errors. Thanks, Andor On Tue, May 15, 2018 at 8:51 PM, Patrick Hunt <[email protected]> wrote: > With three binding +1, one non-binding +1 this vote passes. I will complete > the release steps. > > Thanks everyone, > > Patrick > > > On Tue, May 15, 2018 at 6:31 PM Patrick Hunt <[email protected]> wrote: > > > I ran some clusters using the release candidate and it seems fine to me > > - +1. > > > > Patrick > > > > On Tue, May 15, 2018 at 6:29 PM Patrick Hunt <[email protected]> wrote: > > > >> Thanks Enrico - QuorumKerberosHostBasedAuthTest looks like a test setup > >> issue. See my comments on the jira. > >> > >> Patrick > >> > >> On Mon, May 14, 2018 at 4:34 AM Enrico Olivelli <[email protected]> > >> wrote: > >> > >>> Created this JIRA case, the test is always failing on my laptop > >>> https://issues.apache.org/jira/browse/ZOOKEEPER-3043 > >>> > >>> not blocker for release IMO > >>> > >>> below the error > >>> > >>> Enrico > >>> > >>> Testcase: > >>> org.apache.zookeeper.server.quorum.auth.QuorumKerberosHostBasedAuthTes > t > >>> took 0 sec > >>> Caused an ERROR > >>> Unable to parse:includedir /etc/krb5.conf.d/ > >>> java.lang.RuntimeException: Unable to parse:includedir > /etc/krb5.conf.d/ > >>> at > >>> org.apache.kerby.kerberos.kerb.common.Krb5Parser.load( > Krb5Parser.java:72) > >>> at > >>> > >>> org.apache.kerby.kerberos.kerb.common.Krb5Conf. > addKrb5Config(Krb5Conf.java:47) > >>> at > >>> > >>> org.apache.kerby.kerberos.kerb.client.ClientUtil. > getDefaultConfig(ClientUtil.java:94) > >>> at > >>> > >>> org.apache.kerby.kerberos.kerb.client.KrbClientBase.< > init>(KrbClientBase.java:51) > >>> at > >>> org.apache.kerby.kerberos.kerb.client.KrbClient.<init>( > KrbClient.java:38) > >>> at > >>> > >>> org.apache.kerby.kerberos.kerb.server.SimpleKdcServer.< > init>(SimpleKdcServer.java:54) > >>> at > >>> org.apache.zookeeper.server.quorum.auth.MiniKdc.start( > MiniKdc.java:285) > >>> at > >>> > >>> org.apache.zookeeper.server.quorum.auth.KerberosSecurityTestcase. > startMiniKdc(KerberosSecurityTestcase.java:70) > >>> at > >>> > >>> org.apache.zookeeper.server.quorum.auth.KerberosSecurityTestcase. > setUpSasl(KerberosSecurityTestcase.java:56) > >>> > >>> > >>> > >>> Il giorno lun 14 mag 2018 alle ore 05:39 Michael Han <[email protected]> > >>> ha > >>> scritto: > >>> > >>> > On Sun, May 13, 2018 at 6:26 AM, Enrico Olivelli < > [email protected]> > >>> > wrote: > >>> > > >>> > > +1 (non binding) > >>> > > downloaded, built from source, checked signatures > >>> > > > >>> > > run Apache BookKeeper unit tests using staged Maven Staged > artifacts > >>> and > >>> > > run basic manual tests using this ZK candidate > >>> > > > >>> > > run ZK tests on my Fedora Box > >>> > > got a failure on > >>> > > > >>> org.apache.zookeeper.server.quorum.auth.QuorumKerberosHostBasedAuthTes > t > >>> > > > >>> > > >>> > This is a known flaky test. Unless it fails deterministically, it's > >>> not a > >>> > release blocker. > >>> > > >>> > maybe it is a local dns configuration issue > >>> > > > >>> > > I would like to investigate better on the such failure, can you > >>> remind me > >>> > > how to run a single test with ant and where to find the logs ? > >>> > > >>> > > >>> > One example of running a single test: > >>> > > >>> > ant -Dtestcase=ReconfigRecoveryTest > >>> > -Dtest.method=testCurrentObserverIsParticipantInNewConfig > >>> test-core-java > >>> > > >>> > > >>> > > When I worked on ZK last time I used M. Arshad maven pom.xml but I > >>> lost > >>> > it > >>> > > > >>> > > Enrico > >>> > > > >>> > > > >>> > > > >>> > > Il giorno ven 11 mag 2018 alle ore 21:03 Camille Fournier < > >>> > > [email protected]> ha scritto: > >>> > > > >>> > > > +1 > >>> > > > downloaded, built, ran tests, did some simple manual testing, > >>> verified > >>> > > the > >>> > > > keys. > >>> > > > > >>> > > > C > >>> > > > > >>> > > > On Fri, May 11, 2018 at 1:04 PM, Patrick Hunt <[email protected]> > >>> > wrote: > >>> > > > > >>> > > > > With heartfelt thanks to many contributors, the RC0 for > >>> 3.5.4-beta is > >>> > > > > ready. > >>> > > > > > >>> > > > > 3.5.4-beta is the second beta in the planned 3.5 release line > >>> leading > >>> > > up > >>> > > > to > >>> > > > > a stable 3.5 release. It comprises 113 fixes, improvements, and > >>> new > >>> > > > > features since 3.5.3-beta. > >>> > > > > > >>> > > > > The full release notes is available at: > >>> > > > > > >>> > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa? > >>> > > > > projectId=12310801&version=12340141 > >>> > > > > > >>> > > > > *** Please download, test and vote by May 14th 2018, 10am PT. > *** > >>> > > > > > >>> > > > > Source files: > >>> > > > > > >>> http://people.apache.org/~phunt/zookeeper-3.5.4-beta-candidate-0/ > >>> > > > > > >>> > > > > Maven staging repo: > >>> > > > > https://repository.apache.org/content/groups/staging/org/ > >>> > > > > apache/zookeeper/zookeeper/3.5.4-beta/ > >>> > > > > > >>> > > > > The release candidate tag in git to be voted upon: > >>> release-3.5.4-rc0 > >>> > > > > > >>> > > > > ZooKeeper's KEYS file containing PGP keys we use to sign the > >>> release: > >>> > > > > http://www.apache.org/dist/zookeeper/KEYS > >>> > > > > > >>> > > > > Should we release this candidate? > >>> > > > > > >>> > > > > Regards, > >>> > > > > > >>> > > > > Patrick > >>> > > > > > >>> > > > > >>> > > > >>> > > >>> > >> >
