[HBASE-23881] Netty SASL implementation does not wait for challenge response causing TestShadeSaslAuthenticationProvider failures

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.0.0-alpha-1, 2.3.0
• Fix Version/s: 3.0.0-alpha-1
• Component/s: test
• Hadoop Flags: Reviewed
• Assignee: Josh Elser
• Reporter: Bharath Vissapragada
• Created: 21/Feb/20 18:26
• Updated: 30/Jan/24 21:19
• Resolved: 13/Apr/20 15:07

Description

TestShadeSaslAuthenticationProvider now fails deterministically with the following exception..

java.lang.Exception: Unexpected exception, expected<org.apache.hadoop.hbase.DoNotRetryIOException> but was<java.io.IOException>
	at org.apache.hadoop.hbase.security.provider.example.TestShadeSaslAuthenticationProvider.testNegativeAuthentication(TestShadeSaslAuthenticationProvider.java:233)

The test now fails a different place than before merging HBASE-18095 because the RPCs are also a part of connection setup. We might need to rewrite the test..

Issue Links

• breaks: HBASE-24263 TestDelegationToken is broken
• is broken by: HBASE-18095 Provide an option for clients to find the server hosting META that does not involve the ZooKeeper client
• is related to: HBASE-28110 Align TestShadeSaslAuthenticationProvider between different branches
• relates to: HBASE-24047 [Flakey Tests] Disable TestCustomSaslAuthenticationProvider#testNegativeAuthentication on branch-2.3
• relates to: HBASE-28337 Positive connection test in TestShadeSaslAuthenticationProvider runs with Kerberos instead of Shade authentication
• links to: GitHub Pull Request #1260
• links to: GitHub Pull Request #1502

Sub-Tasks

• Backport fix for "Netty SASL implementation does not wait for challenge response" to branch-2.x: Resolved