You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2018/02/15 00:15:00 UTC
[jira] [Commented] (AMBARI-22837)
AmbariAuthorizationFilterTest.testDoFilter_userNoPermissionsAccess fails
unexpectedly
[ https://issues.apache.org/jira/browse/AMBARI-22837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16364991#comment-16364991 ]
Hudson commented on AMBARI-22837:
---------------------------------
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8733 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8733/])
AMBARI-22837. Remove mocked SecurityContext in (rlevas: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=91462df2291e0cccccb5a1b66d006b9101307e9c])
* (edit) ambari-server/src/test/java/org/apache/ambari/server/security/authorization/AmbariAuthorizationFilterTest.java
> AmbariAuthorizationFilterTest.testDoFilter_userNoPermissionsAccess fails unexpectedly
> -------------------------------------------------------------------------------------
>
> Key: AMBARI-22837
> URL: https://issues.apache.org/jira/browse/AMBARI-22837
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: trunk
> Environment: Ubuntu, 16.04 LTS
> Reporter: Wing Lam
> Priority: Minor
> Labels: pull-request-available
> Fix For: trunk
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> This test requires that the security context not be set up when it runs to pass. If a test that sets up the security context improperly is run before this test, it will fail despite there being no changes in the code.
>
> This can be fixed by clearing the security context, as shown in the pull request.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)