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

Hudson commented on AMBARI-17935:
---------------------------------

SUCCESS: Integrated in Ambari-trunk-Commit #5409 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/5409/])
AMBARI-17935. EU to HDP 2.5 failed since config type (afernandez: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=295e8de48390a4c7f0d28dea732f3ebaacaaa750])
* 
ambari-server/src/main/java/org/apache/ambari/server/serveraction/upgrades/ConfigureAction.java
* 
ambari-server/src/main/resources/stacks/HDP/2.4/upgrades/nonrolling-upgrade-2.5.xml
* 
ambari-server/src/main/resources/stacks/HDP/2.5/services/SQOOP/configuration/sqoop-atlas-application.properties.xml
* 
ambari-server/src/main/resources/stacks/HDP/2.3/upgrades/nonrolling-upgrade-2.5.xml


> EU to HDP 2.5 failed since config type 'sqoop-atlas-application.properties' 
> has not been created
> ------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-17935
>                 URL: https://issues.apache.org/jira/browse/AMBARI-17935
>             Project: Ambari
>          Issue Type: Bug
>          Components: express-upgrade, rolling-upgrade, stacks
>    Affects Versions: 2.4.0
>            Reporter: Alejandro Fernandez
>            Assignee: Alejandro Fernandez
>            Priority: Critical
>             Fix For: 2.4.0
>
>         Attachments: AMBARI-17935.patch
>
>
> STR
> # Deploy Ambari 2.2.2 with HDP 2.4 and Sqoop
> # Kerberize the cluster
> # Upgrade Ambari to 2.4.0
> # Install bits for HDP 2.5 and attempt to perform Express Upgrade
> Observed error during Express Upgrade
> {code}
> Failed on: Updating configuration sqoop-atlas-application.properties
> Server action failed
> {code}
> This happens because the sqoop-atlas-application.properties config in HDP 2.5 
> hasn't been created yet since it doesn't actually have any configs. To fix 
> it, add some configs so the merging process creates the new config type.



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

Reply via email to