[
https://issues.apache.org/jira/browse/AMBARI-11734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14575292#comment-14575292
]
Hadoop QA commented on AMBARI-11734:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12738027/AMBARI-11734.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 2 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The test build failed in ambari-server
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/3064//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/3064//console
This message is automatically generated.
> 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)
