[ 
https://issues.apache.org/jira/browse/HBASE-24303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17099997#comment-17099997
 ] 

Nick Dimiduk commented on HBASE-24303:
--------------------------------------

2.3 nightly had a failure of {{TestInfoServerACL}} on both JDKs and this is the 
most suspicious ticket in the list. Mind taking a look?

https://builds.apache.org/job/HBase%20Nightly/job/branch-2.3/65/testReport/junit/org.apache.hadoop.hbase.http/TestInfoServersACL/health_checks___yetus_jdk11_hadoop3_checks___testJmxAvailableForAdmins/

> Undo core of parent TestSecureRESTServer change; use fix over in HBASE-24280 
> instead
> ------------------------------------------------------------------------------------
>
>                 Key: HBASE-24303
>                 URL: https://issues.apache.org/jira/browse/HBASE-24303
>             Project: HBase
>          Issue Type: Sub-task
>    Affects Versions: 3.0.0-alpha-1, 2.3.0
>            Reporter: Michael Stack
>            Assignee: Michael Stack
>            Priority: Major
>             Fix For: 3.0.0-alpha-1, 2.3.0
>
>
> Parent issue puts in a place that makes TestSecureRESTServer pass up on 
> jenkins by shoving into the dependency list the jersey1 ServletContainer. 
> Root issue was change in how we specified profiles in nightlies; both hadoop3 
> and hadoop2 were mistakenly active (HBASE-24280). This issue is about undoing 
> the dependency insertion after fix for HBASE-24280 goes in.
> Don't want to revert the parent. It has cleanups that should stay.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to