[jira] [Commented] (AMBARI-21094) Customize services shows inconsistent config-groups after clicking on Back button

["Hadoop QA (JIRA)" <ji...@apache.org>]

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

Hadoop QA commented on AMBARI-21094:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12869335/AMBARI-21094.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include any new or modified tests.
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

        {color:red}-1 release audit{color}.  The applied patch generated 1 release audit warnings.

    {color:red}-1 javac{color}.  The patch appears to cause the [build to fail|https://builds.apache.org/job/Ambari-trunk-test-patch/11607//artifact/patch-work/patchJavacWarnings.txt].

Release audit warnings: https://builds.apache.org/job/Ambari-trunk-test-patch/11607//artifact/patch-work/patchReleaseAuditProblems.txt
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/11607//console

This message is automatically generated.

> Customize services shows inconsistent config-groups after clicking on Back button
> ---------------------------------------------------------------------------------
>
>                 Key: AMBARI-21094
>                 URL: https://issues.apache.org/jira/browse/AMBARI-21094
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-web
>            Reporter: Amruta Borkar
>            Assignee: Amruta Borkar
>             Fix For: trunk
>
>         Attachments: AMBARI-21094.patch
>
>
> Steps to reproduce:
> 1. Go to Customize Services screen
> 2. Create a Custom HostGroup
> 3. Click Back button
> 4. Click Next Button
> 5. See that Custom Hostgroup still exists, but all the data including assigned hosts is erased. 
> Ambari typically erases all the changes when clicked on Back button, because the Custom HostGroup is not deleted but data related to it is deleted by Ambari cluster state goes in inconsistent state.



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