You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Antonenko Alexander (JIRA)" <ji...@apache.org> on 2015/03/26 16:43:55 UTC
[jira] [Created] (AMBARI-10219) Ambari should very explicitly show
in a globally visible area when config form validation errors occurred
Antonenko Alexander created AMBARI-10219:
--------------------------------------------
Summary: 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
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)