[HBASE-24280] Hadoop2 and Hadoop3 profiles being activated simultaneously causing test failures

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.3.0, 2.2.6
• Hadoop Flags: Reviewed
• Assignee: Istvan Toth
• Reporter: Josh Elser
• Created: 29/Apr/20 00:05
• Updated: 06/Jul/20 06:22
• Resolved: 03/Jun/20 23:39

Description

ndimiduk pointed out that, after this change went in, TestSecureRESTServer started failing with Hadoop3 on branch-2.3

https://builds.apache.org/job/HBase%20Nightly/job/branch-2.3/56/

Of course, I ran this with 1.8.0_241 and Maven 3.6.33 and it passed mvn clean package -Dtest=TestSecureRESTServer -Dhadoop.profile=3.0 -DfailIfNoTests=false

FYI stoty in case you can repro a failure and want to dig in. Feel free to re-assign.

It looks like we didn't have a nightly run of branch-2.2 due to docker container build issues. Will be interesting to see if it fails there. It did not fail the master nightly.

Issue Links

• is caused by: HBASE-24198 Skip hadoop2 check for master branch
• is related to: HBASE-24223 The -Phadoop-3.0 option does not work on branch-2 and branch-2.3 with JDK11
• is related to: HBASE-24319 Clearly document how profiles for the sake of Hadoop compatibility work across all branches
• relates to: HBASE-24215 [Flakey Tests] [ERROR] TestSecureRESTServer java.lang.NoClassDefFoundError: com/sun/jersey/core/spi/factory/AbstractRuntimeDelegate
• links to: GitHub Pull Request #1847
• links to: GitHub Pull Request #1849

Sub-Tasks

• Hadoop2&Hadoop3 profiles are both active when pre-commit PR builds run: Resolved