You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Robert Levas (JIRA)" <ji...@apache.org> on 2018/06/20 19:15:00 UTC

[jira] [Resolved] (AMBARI-24141) Rolling restarts not working when Kerberos Auto sign in is enabled for Ambari

     [ https://issues.apache.org/jira/browse/AMBARI-24141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Levas resolved AMBARI-24141.
-----------------------------------
    Resolution: Fixed

> Rolling restarts not working when Kerberos Auto sign in is enabled for Ambari
> -----------------------------------------------------------------------------
>
>                 Key: AMBARI-24141
>                 URL: https://issues.apache.org/jira/browse/AMBARI-24141
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.6.0
>            Reporter: Robert Levas
>            Assignee: Robert Levas
>            Priority: Blocker
>              Labels: pull-request-available
>             Fix For: 2.7.0
>
>          Time Spent: 2.5h
>  Remaining Estimate: 0h
>
> Rolling restarts not working when Kerberos Auto sign in is enabled for Ambari.  This is due to a missing user ID value in the {{requestschedule}} table, resulting in the Rolling Restart operation aborting with no deals in the ambari-server.log file.
> ||schedule_id||cluster_id||authenticated_user_id||create_user||update_user||last_execution_status||
> |2|2|-1|rlevas|rlevas|IN_PROGRESS|
> This occurs because the {{org.springframework.security.core.Authentication}} class stored in Ambari's SecurityContext for the authenticated user does not contain the authenticated user's ID data. Adjustments need to be made to the infrastructure to capture this data upon login and then retrieve it later, when needed. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)