You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Antonenko Alexander (JIRA)" <ji...@apache.org> on 2016/09/27 15:31:20 UTC
[jira] [Updated] (AMBARI-18474) Kerberos wizard loses request id on
server restart
[ https://issues.apache.org/jira/browse/AMBARI-18474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Antonenko Alexander updated AMBARI-18474:
-----------------------------------------
Attachment: Screen Shot 2016-09-20 at 6.37.29 PM.png
> Kerberos wizard loses request id on server restart
> --------------------------------------------------
>
> Key: AMBARI-18474
> URL: https://issues.apache.org/jira/browse/AMBARI-18474
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 2.2.2
> Reporter: Antonenko Alexander
> Assignee: Antonenko Alexander
> Priority: Critical
> Fix For: 2.5.0
>
> Attachments: Screen Shot 2016-09-20 at 6.37.29 PM.png
>
>
> *Problem*
> - Kerberos wizard create principals action timed out
> - To increase task timeout we had to restart the server
> - On restart wizard comes up wit ha spinner, no error no indication of what is happening
> - had to post a last request id through js console for work to resume.
> - Quitting a wizard means users has to start from the very beginning, on a 1300 node cluster that is not feasible.
> *Expected behavior*:
> - If the last request id was not perisisted by UI, on restart the last request id needs to be retrieved and check for context info to resume from where the user left the wizard.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)