[jira] [Commented] (AMBARI-11925) Kerkeros Service Configs: KDC Type Value is corrupted

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

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

Hadoop QA commented on AMBARI-11925:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12739608/AMBARI-11925_01.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: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 .

Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/3185//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/3185//console

This message is automatically generated.

> Kerkeros Service Configs: KDC Type Value is corrupted
> -----------------------------------------------------
>
>                 Key: AMBARI-11925
>                 URL: https://issues.apache.org/jira/browse/AMBARI-11925
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-web
>    Affects Versions: 2.1.0
>            Reporter: Robert Levas
>            Assignee: Robert Levas
>              Labels: kerberos, kerberos-wizard
>             Fix For: 2.1.0
>
>         Attachments: AMBARI-11925_01.patch
>
>
> *Steps to reproduce:*
> 1. Install Kerberos on the Cluster
> 2. Go to Kerberos Configs
> 3. Change any value in the configuration
> 4. Click Save and Confirm
> *Expect Result:*
> The KDC Type Value should remain unchanged.
> The user should be able to make further modifications to the configs after this points.
> *Actual Result:*
> The Kerberos KDC Type Value is changed to the descriptive value and thus is unexpected.  Since this is a required field, but cannot be edited, the user can no longer save any changes after this point



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)