[DRILL-5383] Several impersonation unit tests fail in unit test

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Cannot Reproduce
• Assignee: Unassigned
• Reporter: Chunhui Shi
• Created: 24/Mar/17 18:57
• Updated: 19/Jul/22 08:40
• Resolved: 19/Jul/22 08:40

Description

Run several round unit tests and got these errors:
Failed tests:
TestInboundImpersonationPrivileges.twoTargetGroups:135->run:62 proxyName: user3_2 targetName: user4_2 expected:<true> but was:<false>
TestInboundImpersonationPrivileges.oneTargetGroup:118->run:62 proxyName: user5_1 targetName: user4_2 expected:<true> but was:<false>
TestInboundImpersonationPrivileges.twoTargetUsers:126->run:62 proxyName: user5_2 targetName: user0_2 expected:<true> but was:<false>

Tests in error:
TestDrillbitResilience.memoryLeaksWhenCancelled:890->assertCancelledWithoutException:532 »
TestInboundImpersonation.selectChainedView:136 » org.apache.drill.common.exce...
TestImpersonationQueries.org.apache.drill.exec.impersonation.TestImpersonationQueries » UserRemote

Notice that if I run unit test in my setup, which has different settings.xml for maven to point to our internal repository I often (maybe 1 out of 2 runs) got different error at TestOptionsAuthEnabled#updateSysOptAsUserInAdminGroup,

Since the error is quite consistent when the unit test is built on different nodes. I guess when we introduce more jars(kerby?) for unit tests we may not do the exclusion enough so conflicts are different for different builds.

We should be able to find out why it failed by remote debugging into these particular tests.

If we could not address this issue in one or two days, this JIRA should be used to disable these tests for now.

Issue Links

• is related to: DRILL-5387 TestBitBitKerberos and TestUserBitKerberos cause sporadic unit test failures