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

Hudson commented on AMBARI-11734:
---------------------------------

SUCCESS: Integrated in Ambari-trunk-Commit #2833 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/2833/])
AMBARI-11734 - Missing Falcon conf files after rolling upgrade  
(jonathanhurley) (jhurley: 
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=c33b8ee26849accf516ca0afd0bb811513e65c9c)
* ambari-server/src/test/python/stacks/2.1/FALCON/test_falcon_server.py
* 
ambari-common/src/main/python/resource_management/libraries/functions/tar_archive.py
* 
ambari-server/src/main/resources/common-services/KNOX/0.5.0.2.2/package/scripts/upgrade.py
* 
ambari-server/src/main/resources/common-services/FLUME/1.4.0.2.0/package/scripts/flume_upgrade.py
* 
ambari-server/src/main/resources/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_server_upgrade.py
* 
ambari-server/src/main/resources/common-services/FALCON/0.5.0.2.1/package/scripts/falcon_server_upgrade.py
* ambari-server/src/test/python/stacks/2.0.6/OOZIE/test_oozie_server.py


> Missing Falcon conf files after rolling upgrade 
> ------------------------------------------------
>
>                 Key: AMBARI-11734
>                 URL: https://issues.apache.org/jira/browse/AMBARI-11734
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.1.0
>            Reporter: Jonathan Hurley
>            Assignee: Jonathan Hurley
>            Priority: Critical
>             Fix For: 2.1.0
>
>         Attachments: AMBARI-11734.patch
>
>
> Performed manual rolling upgrade from 2.2.7 -> 2.3.0 using Ambari 
> (#VERSION_NUMBER=2.1.0-1900)
> After upgrade, Falcon was not writing log into the falcon.application.log. 
> The conf dir (upgraded 2.3.0) did not have the following conf files from 
> 2.2.7:
> 1. log4j.xml
> 2. prism.keystore
> 3. falcon_env.ini



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

Reply via email to