You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Andrii Tkach (JIRA)" <ji...@apache.org> on 2015/09/17 12:25:46 UTC
[jira] [Created] (AMBARI-13123) Usability: do not force redirect
the user to the currently running wizard if another user logs in
Andrii Tkach created AMBARI-13123:
-------------------------------------
Summary: Usability: do not force redirect the user to the currently running wizard if another user logs in
Key: AMBARI-13123
URL: https://issues.apache.org/jira/browse/AMBARI-13123
Project: Ambari
Issue Type: Task
Components: ambari-web
Affects Versions: 2.0.0
Reporter: Andrii Tkach
Assignee: Andrii Tkach
Priority: Critical
Fix For: 2.2.0
When a user initiates "major" cluster reconfiguration operations, such as Enable NameNode HA, Enable Kerberos, Add Hosts, Add Services, etc, the user forces any user who accesses Ambari Web to be redirected to the wizard.
This unnecessarily restricts what the users can do, and also it is dangerous because multiple users may interact with the wizard (or keep the wizards open and multiple instances can make API calls with side effects, causing failure).
If users different from who initiated the major reconfiguration operation logs in while the operation is still going on, the user should not be force redirected, but instead be able to access the cluster in read-only mode with some indication that "NameNode HA is being enabled", etc (much like what happens when Rolling Upgrade is happening).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)