[
https://issues.apache.org/jira/browse/AMBARI-6532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jaimin D Jetly updated AMBARI-6532:
-----------------------------------
Description:
*STR:*
1) Deploy cluster
2) Go through either security, Add Service or Enable NameNode HA
2) Go to the final step of the wizard
3) Click 'Done'
*Actual result:* After clicking 'Done' there is modal window with next message:
"Error in persisting web client state at ambari server: Error 0"
After that Ambari works correctly, but once other browser opens UI (or do
logout/login), last step of the wizard appears again. Probably, it is
consequence from described issue.
*Reason:*
The calls for user preferences are made asynchronous lately.
App.clusterStatus.setClusterStatus function that used App.userPref mixin's
postUserPref method was made asynchronous. App.clusterStatus.setClusterStatus
function is normally called at the end of the wizard to state to the server
persist key that wizard is completed and then window.location.reload() function
is called. As the prior call was changed to asynchronous, browser window was
reloaded before the client even successfully submitted the Ajax call and the
web state of the wizard completion was not saved on the server.
was:
*STR:*
1) Deploy cluster
2) Go through either security, Add Service or Enable NameNode HA
2) Go to the final step of the wizard
3) Click 'Done'
*Actual result:* After clicking 'Done' there is modal window with next message:
"Error in persisting web client state at ambari server: Error 0"
After that Ambari works correctly, but once other browser opens UI (or do
logout/login), last step of the wizard appears again. Probably, it is
consequence from described issue.
> Error message appears after last step of Enable security, NameNode HA and Add
> Service wizard
> --------------------------------------------------------------------------------------------
>
> Key: AMBARI-6532
> URL: https://issues.apache.org/jira/browse/AMBARI-6532
> Project: Ambari
> Issue Type: Bug
> Components: client
> Affects Versions: 1.7.0
> Reporter: Jaimin D Jetly
> Assignee: Jaimin D Jetly
> Fix For: 1.7.0
>
> Attachments: AMBARI-6532.patch
>
>
> *STR:*
> 1) Deploy cluster
> 2) Go through either security, Add Service or Enable NameNode HA
> 2) Go to the final step of the wizard
> 3) Click 'Done'
> *Actual result:* After clicking 'Done' there is modal window with next
> message: "Error in persisting web client state at ambari server: Error 0"
> After that Ambari works correctly, but once other browser opens UI (or do
> logout/login), last step of the wizard appears again. Probably, it is
> consequence from described issue.
> *Reason:*
> The calls for user preferences are made asynchronous lately.
> App.clusterStatus.setClusterStatus function that used App.userPref mixin's
> postUserPref method was made asynchronous. App.clusterStatus.setClusterStatus
> function is normally called at the end of the wizard to state to the server
> persist key that wizard is completed and then window.location.reload()
> function is called. As the prior call was changed to asynchronous, browser
> window was reloaded before the client even successfully submitted the Ajax
> call and the web state of the wizard completion was not saved on the server.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
