ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jaimin D Jetly (JIRA)" <>
Subject [jira] [Commented] (AMBARI-2387) Security Wizard: the user gets stuck after quitting Security wizard and starting it again
Date Sat, 15 Jun 2013 00:25:20 GMT


Jaimin D Jetly commented on AMBARI-2387:

Each stage carries set of information including requestId. I noticed that you are maintaining
the state of the stages in local storage even on quitting security wizard or doing re-run
of the wizard. 

We should always stop all services before applying configuration. If We maintain the state
of stages on quitting, We can definitely quit and re-run the wizard polling on same requestId.
But if any action is done between quitting and re-running the wizard, stored stages are unaware
of this. For example if we quit the wizard While its stopping the service, start all services
individually and then re-run the wizard, it will declare stop stage as completed right from
start as stored requestId is polled which is already completed. In reality services were started
outside of wizard by us which are required to stop before applying configurations. 

> Security Wizard: the user gets stuck after quitting Security wizard and starting it again
> -----------------------------------------------------------------------------------------
>                 Key: AMBARI-2387
>                 URL:
>             Project: Ambari
>          Issue Type: Bug
>          Components: client
>    Affects Versions: 1.2.5
>            Reporter: Andrii Tkach
>            Assignee: Andrii Tkach
>             Fix For: 1.2.5
>         Attachments: AMBARI-2387.patch
> On Adding Security or disabling security, We stop all services. Revisiting it again stucks
web-ui as the initial "Stop all services " request is ongoing and we generate another request.
> If a request with "stop all services" context is already being polled then We should
keep polling on that request.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message