ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-20178) Add authentication for Topology tasks
Date Thu, 02 Mar 2017 16:56:45 GMT

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

Hadoop QA commented on AMBARI-20178:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12855652/AMBARI-20178_v3.patch
  against trunk revision .

    {color:red}-1 patch{color}.  Top-level trunk compilation may be broken.

Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/10845//console

This message is automatically generated.

> Add authentication for Topology tasks
> -------------------------------------
>
>                 Key: AMBARI-20178
>                 URL: https://issues.apache.org/jira/browse/AMBARI-20178
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>            Reporter: Sandor Magyari
>            Assignee: Sandor Magyari
>             Fix For: 3.0.0
>
>         Attachments: AMBARI-20178.patch, AMBARI-20178_v2.patch, AMBARI-20178_v3.patch
>
>
> Replaying persisted requests on ambari-server start fail due to authorization error.
> Requests issued by an authenticated user that doesn't succeed are replayed on ambari
server start. The replay is issued during the server start, so there is no authenticated user
in the security context, thus the request fail over and over till the retry period is exceeded
and this repeats when the server is restarted.
> The unprocessed requests get stuck in the database.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message