ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-20302) Despite user selecting not to apply Config Changes, Changes are being applied
Date Fri, 03 Mar 2017 16:29:45 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-20302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15894668#comment-15894668
] 

Hadoop QA commented on AMBARI-20302:
------------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12855878/AMBARI-20302.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/10875//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/10875//console

This message is automatically generated.

> Despite user selecting not to apply Config Changes, Changes are being applied
> -----------------------------------------------------------------------------
>
>                 Key: AMBARI-20302
>                 URL: https://issues.apache.org/jira/browse/AMBARI-20302
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-web
>    Affects Versions: 2.5.0
>            Reporter: Aleksandr Kovalenko
>            Assignee: Aleksandr Kovalenko
>            Priority: Critical
>             Fix For: 2.5.0
>
>         Attachments: AMBARI-20302_branch-2.5.patch, AMBARI-20302.patch
>
>
> Steps:
> 1) On an existing cluster, Delete Ambari Infra service
> 2) At time of deletion, there will be a popup which shows Recommended Config changes
> 3) Unselect the recommended config change and continue
> Expected:
> Config change should not be applied
> Acutal:
> Config change was applied regardless



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message