[jira] [Commented] (AMBARI-24999) Disallow changing Kerberos-related configs in Add Service request

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

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

Hudson commented on AMBARI-24999:
---------------------------------

FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #10360 (See [https://builds.apache.org/job/Ambari-trunk-Commit/10360/])
AMBARI-24999. Disallow changing Kerberos-related configs in Add Service (github: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=e70dd4e7434bc3828629d329684a12b574dfd9d3])
* (edit) ambari-server/src/main/java/org/apache/ambari/server/topology/addservice/RequestValidator.java
* (edit) ambari-server/src/test/java/org/apache/ambari/server/topology/addservice/RequestValidatorTest.java


> Disallow changing Kerberos-related configs in Add Service request
> -----------------------------------------------------------------
>
>                 Key: AMBARI-24999
>                 URL: https://issues.apache.org/jira/browse/AMBARI-24999
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-server
>    Affects Versions: 2.8.0
>            Reporter: Doroszlai, Attila
>            Assignee: Doroszlai, Attila
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 2.8.0
>
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> Ambari should not allow a user to set configurations in the {{kerberos-env}} and {{krb5-conf}} configuration types within the complex Add Service request.  Generally, setting these configurations on an existing Kerberized cluster could be problematic, since existing services already depend upon the existing configuration to interact with the KDC.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)