[
https://issues.apache.org/jira/browse/AMBARI-15186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15168656#comment-15168656
]
Hadoop QA commented on AMBARI-15186:
------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12790090/AMBARI-15186.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
ambari-web.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/5580//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/5580//console
This message is automatically generated.
> Config saving discards Capacity-scheduler changes
> -------------------------------------------------
>
> Key: AMBARI-15186
> URL: https://issues.apache.org/jira/browse/AMBARI-15186
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 2.2.2
> Reporter: Andrii Babiichuk
> Assignee: Andrii Babiichuk
> Priority: Critical
> Fix For: 2.2.2
>
> Attachments: AMBARI-15186.patch, AMBARI-15186_branch_2.2.patch
>
>
> STR
> 1) Install Yarn
> 2) Add new line to Capacity Scheduler config
> 3) Click save
> Result: Changes are not saved.
> Also config comparison works wrong for Capacity Scheduler.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
