You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Richard Zang (JIRA)" <ji...@apache.org> on 2015/05/17 03:48:59 UTC
[jira] [Updated] (AMBARI-11193) Configs: edited a toggle and
control reverts
[ https://issues.apache.org/jira/browse/AMBARI-11193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Richard Zang updated AMBARI-11193:
----------------------------------
Attachment: AMBARI-11193.patch
> Configs: edited a toggle and control reverts
> --------------------------------------------
>
> Key: AMBARI-11193
> URL: https://issues.apache.org/jira/browse/AMBARI-11193
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 2.1.0
> Reporter: Richard Zang
> Assignee: Richard Zang
> Fix For: 2.1.0
>
> Attachments: AMBARI-11193.patch
>
>
> 1) edited the YARN pre-emption toggle in escape hatch
> 2) put in bogus info
> 3) the ui (correctly) would not let out of escape hatch
> 4) saved config w/o warning (i would have thought it would have validated this is bogus?)
> 5) then when the ui refresh, the ui was out of escape hatch (which should have been impossible because the value was bogus)
> 6) if I escape hatch again, bogus value is there
> Seem two problems:
> - expected some warning this value is bogus for the config, especially these true/false toggles
> - expected the ui to realize the value is bogus and not revert to non-escape hatch mode
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)