[
https://issues.apache.org/jira/browse/AMBARI-14169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15042623#comment-15042623
]
Hudson commented on AMBARI-14169:
---------------------------------
ABORTED: Integrated in Ambari-branch-2.2 #10 (See
[https://builds.apache.org/job/Ambari-branch-2.2/10/])
AMBARI-14169. SYNC SOURCE property needs to be maintained for RU (2.2.x
(smohanty:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=bf9d6b23b50720e8fa36bcef490a4c7cdd90be3f])
* ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/upgrade-2.3.xml
*
ambari-server/src/main/resources/stacks/HDP/2.2/upgrades/nonrolling-upgrade-2.3.xml
* ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/config-upgrade.xml
*
ambari-server/src/main/resources/common-services/RANGER/0.4.0/configuration/usersync-properties.xml
> SYNC SOURCE property needs to be maintained for RU (2.2.x to 2.3.x)
> -------------------------------------------------------------------
>
> Key: AMBARI-14169
> URL: https://issues.apache.org/jira/browse/AMBARI-14169
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.2.0
> Reporter: Gautam Borad
> Assignee: Gautam Borad
> Fix For: 2.2.0
>
> Attachments: AMBARI-14169.1.patch, AMBARI-14169.patch
>
>
> During Rolling Upgrade (Express) Sync Source property in Ranger User Info tab
> needs to be handled.
> *Issue*:
> Express Upgrade from HDP-2.2.10.0-3394 to HDP-2.3.4.0-3346 with AD sync
> source and authentication
> *After Upgrade*:
> Sync source was UNIX instead of LDAP/AD.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
