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

Robert Kanter updated OOZIE-1959:
---------------------------------
    Attachment: OOZIE-1959.patch
                OOZIE-1959_branch-4.1.patch

The patch fixes the test by using "127.0.0.1" instead of "localhost" for the 
zookeeper principal.  I've also moved it into a new maven module so that it 
will get it's own JVM automatically, and we can include it in normal test runs.

The branch-4.1 and trunk patches differ only in the pom versioning and a minor 
pom conflict.

> TestZKUtilsWithSecurity fails
> -----------------------------
>
>                 Key: OOZIE-1959
>                 URL: https://issues.apache.org/jira/browse/OOZIE-1959
>             Project: Oozie
>          Issue Type: Bug
>    Affects Versions: trunk, 4.1.0
>            Reporter: Robert Kanter
>            Assignee: Robert Kanter
>            Priority: Blocker
>             Fix For: trunk, 4.1.0
>
>         Attachments: OOZIE-1959.patch, OOZIE-1959_branch-4.1.patch
>
>
> 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.3.4#6332)

Reply via email to