[jira] [Updated] (KUDU-2994) KuduTestHarness fails to start with NTP error when using kudu-binary 1.11.0

["Adar Dembo (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/KUDU-2994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Adar Dembo updated KUDU-2994:
-----------------------------
    Target Version/s: 1.11.1
            Priority: Critical  (was: Major)

[~aserbin] do you think we can address this in time for 1.11.1? The binary artifact is unusable until this is fixed, right?

> KuduTestHarness fails to start with NTP error when using kudu-binary 1.11.0
> ---------------------------------------------------------------------------
>
>                 Key: KUDU-2994
>                 URL: https://issues.apache.org/jira/browse/KUDU-2994
>             Project: Kudu
>          Issue Type: Bug
>          Components: test
>    Affects Versions: 1.11.0
>            Reporter: Greg Solovyev
>            Priority: Critical
>
> I tried using Kudu binary jars today (version 1.11.0) and I get the following exception, when trying to initialize the harness:
> {code:java}
> java.io.IOException: failed to start NTP server 0: Unable to canonicalize /var/folders/kz/3479cpp131b6w8gp2fjpz0fw0000gp/T/kudu-binary-jar5655318054000350912/kudu-binary-1.11.0-osx-x86_64/bin/chronyd: No such file or directory
>     at org.apache.kudu.test.cluster.MiniKuduCluster.sendRequestToCluster(MiniKuduCluster.java:169)
>     at org.apache.kudu.test.cluster.MiniKuduCluster.start(MiniKuduCluster.java:234)
>     at org.apache.kudu.test.cluster.MiniKuduCluster.access$300(MiniKuduCluster.java:71)
>     at org.apache.kudu.test.cluster.MiniKuduCluster$MiniKuduClusterBuilder.build(MiniKuduCluster.java:658)
>     at org.apache.kudu.test.KuduTestHarness.before(KuduTestHarness.java:140)
>     at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:46)
>     at org.apache.kudu.test.junit.RetryRule$RetryStatement.doOneAttempt(RetryRule.java:215)
>     at org.apache.kudu.test.junit.RetryRule$RetryStatement.evaluate(RetryRule.java:232)
>     at org.junit.rules.RunRules.evaluate(RunRules.java:20)
>     at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
>     at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
>     at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
>     at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
>     at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
>     at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
>     at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
>     at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
>     at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
>     at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:89)
>     at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:41)
>     at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:541)
>     at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:763)
>     at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:463)
>     at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:209)
> {code}
> the same test works with kudu-binary 1.10.0



--
This message was sent by Atlassian Jira
(v8.3.4#803005)