[
https://issues.apache.org/jira/browse/OOZIE-1959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Kanter updated OOZIE-1959:
---------------------------------
Priority: Blocker (was: Major)
More specifically, the problem occurs with ZooKeeper 3.4.6, which we switched
to with OOZIE-1906 when Curator was updated (we had ZooKeeper 3.4.5 before).
When I force ZooKeeper 3.4.5 with the current Curator, it works correctly, so
hopefully it's just some minor config change that we need to figure out that
changed between ZK 3.4.5 and 3.4.6.
> TestZKUtilsWithSecurity fails
> -----------------------------
>
> Key: OOZIE-1959
> URL: https://issues.apache.org/jira/browse/OOZIE-1959
> Project: Oozie
> Issue Type: Bug
> Affects Versions: trunk
> Reporter: Robert Kanter
> Assignee: Robert Kanter
> Priority: Blocker
> Fix For: trunk
>
>
> TestZKUtilsWithSecurity fails:
> {noformat}
> -------------------------------------------------------
> T E S T S
> -------------------------------------------------------
> Picked up _JAVA_OPTIONS: -Djava.awt.headless=true
> Concurrency config is parallel='classes', perCoreThreadCount=false,
> threadCount=1, useUnlimitedThreads=false
> 2014-07-31 16:44:33.786 java[38553:da03] Unable to load realm info from
> SCDynamicStore
> Running org.apache.oozie.util.TestZKUtilsWithSecurity
> Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 71.418 sec
> <<< FAILURE!
> Results :
> Tests in error:
> testCheckAndSetACLs(org.apache.oozie.util.TestZKUtilsWithSecurity): E1700:
> Issue communicating with ZooKeeper: KeeperErrorCode = AuthFailed for /services
> testNewUsingACLs(org.apache.oozie.util.TestZKUtilsWithSecurity):
> KeeperErrorCode = AuthFailed for /oozie
> Tests run: 2, Failures: 0, Errors: 2, Skipped: 0
> {noformat}
> It would also be good to get test-patch to run this (it currently does not
> because it needs to be run in a separate JVM as it changes JVM security
> settings that can't be unchanged); I think we can actually just create a new
> module for ZK Security tests (and move this test there) because each module
> uses a new JVM.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
