[
https://issues.apache.org/jira/browse/AMBARI-23895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16480750#comment-16480750
]
Hudson commented on AMBARI-23895:
---------------------------------
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #9289 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/9289/])
AMBARI-23895 Configuration Validation is throwing errors on correct
(1963907+atkach:
[https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=0bae7049abf2dc3f4e870846eef8d82b235f5a05])
* (edit) ambari-web/app/mixins/common/serverValidator.js
> Configuration Validation is throwing errors on correct configuration
> --------------------------------------------------------------------
>
> Key: AMBARI-23895
> URL: https://issues.apache.org/jira/browse/AMBARI-23895
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 2.7.0
> Reporter: Andrii Tkach
> Assignee: Andrii Tkach
> Priority: Blocker
> Labels: pull-request-available
> Fix For: 2.7.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> During installation if you change configuration there are a lot of
> configuration validation errors that appear to be using > and not >=. See
> screenshot. This results in 20+ things for the user to review, but most of
> them are correct because the value is 19 and we're asking them to set it to
> 19.
> Steps to Reproduce:
> # Install Ambari 2.7
> # Choose ZK, HDFS, YARN, Hive
> # Double the *Minimum Container Size (Memory)* during the *All
> Configurations* step
> # Observe that the configuration validations are mostly asking us to change
> values to what they already are
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
