[
https://issues.apache.org/jira/browse/AMBARI-8467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14227769#comment-14227769
]
Hadoop QA commented on AMBARI-8467:
-----------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12684076/AMBARI-8467.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/771//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/771//console
This message is automatically generated.
> Ambari Web: Lock navigation down while upgrade is happening
> -----------------------------------------------------------
>
> Key: AMBARI-8467
> URL: https://issues.apache.org/jira/browse/AMBARI-8467
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
> Affects Versions: 2.0.0
> Reporter: Andrii Tkach
> Assignee: Andrii Tkach
> Fix For: 2.0.0
>
> Attachments: AMBARI-8467.patch
>
>
> We need to lock down Ambari Web UI navigation while an upgrade is happening.
> For Ambari Admins and Cluster Operators:
> * *The user is treated as a read-only user* so cluster operation controls are
> not shown, except for Upgrade related controls.
> Cluster Read-only users:
> * Upgrade progress has no effect on read-only users; they can still navigate
> as before.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
