[
https://issues.apache.org/jira/browse/AMBARI-12419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14628574#comment-14628574
]
Hudson commented on AMBARI-12419:
---------------------------------
FAILURE: Integrated in Ambari-trunk-Commit #3119 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/3119/])
AMBARI-12419 Final flag not preserved after enabling security (dsen) (dsen:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=1eb38c298b228a73ae5fd5127769b7b75e64f374)
*
ambari-server/src/test/java/org/apache/ambari/server/state/ConfigHelperTest.java
* ambari-server/src/main/java/org/apache/ambari/server/state/ConfigHelper.java
> Final flag not preserved after enabling security
> ------------------------------------------------
>
> Key: AMBARI-12419
> URL: https://issues.apache.org/jira/browse/AMBARI-12419
> Project: Ambari
> Issue Type: Bug
> Affects Versions: 2.1.0
> Reporter: Dmytro Sen
> Assignee: Dmytro Sen
> Priority: Blocker
> Fix For: 2.1.1
>
> Attachments: AMBARI-12419_4.patch
>
>
> The issue is noticed in an RU cluster where rolling upgrade has to be
> performed with ambari2.1.0. After installing dal bits we are setting final
> flag for a property 'tez.am.resource.memory.mb' to final which you can see in
> V3 config of the cluster. Then enabling security and HA is performed. After
> these operations we see that the final flag was turned off. Upon checking the
> versions, V4 doesn't have this final flag and changes between V3 and V4 is
> that, security is enabled at V4. (HiveServer2 Authentication is set to
> kerberos in V4 not in V3).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
