[
https://issues.apache.org/jira/browse/AMBARI-10219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14382145#comment-14382145
]
Hadoop QA commented on AMBARI-10219:
------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12707518/AMBARI-10219.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 2 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/2146//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/2146//console
This message is automatically generated.
> Ambari should very explicitly show in a globally visible area when config
> form validation errors occurred
> ---------------------------------------------------------------------------------------------------------
>
> Key: AMBARI-10219
> URL: https://issues.apache.org/jira/browse/AMBARI-10219
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
> Affects Versions: 1.7.0
> Reporter: Antonenko Alexander
> Assignee: Antonenko Alexander
> Priority: Critical
> Fix For: 2.1.0
>
> Attachments: AMBARI-10219.patch, configs-alert-block.jpg,
> filter-issues.jpg
>
>
> PROBLEM: If a validation error occurs in a configuration field which is
> currently not visible because the group it's part of (e.g. "Advanced
> yarn-site") is rolled-up, the save button won't be enabled and it won't be
> obvious as to why this is the case.
> In the cause which led me to file this request, customer did an upgrade to
> Ambari 1.7/HDP 2.2. During the upgrade, he did not set the value of
> {{yarn.resourcemanager.fs.state-store.uri}}. Subsequently, since Ambari
> expects this value to be ' ' (single space), the YARN configuration form
> would never pass validation, so he could not change YARN for no obvious
> reason. Since he never expanded the "Advanced yarn-site" group, he never saw
> this, leading to wasted time. If Ambari would have put something next to the
> Save button indicating there was an error, and maybe even linked to it, this
> could have been avoided.
> BUSINESS IMPACT: Since it's not clear why the form won't save, this results
> in wasted time and unnecessary support cases.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
