[
https://issues.apache.org/jira/browse/AMBARI-9756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14334043#comment-14334043
]
Hadoop QA commented on AMBARI-9756:
-----------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12700261/AMBARI-9756.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:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/1781//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/1781//console
This message is automatically generated.
> Oozie Service Check Fails During Upgrade Due To Incorrect Example Directory
> ---------------------------------------------------------------------------
>
> Key: AMBARI-9756
> URL: https://issues.apache.org/jira/browse/AMBARI-9756
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.0.0
> Reporter: Jonathan Hurley
> Assignee: Jonathan Hurley
> Priority: Critical
> Fix For: 2.0.0
>
> Attachments: AMBARI-9756.patch
>
>
> Oozie Server service check fails with 'dirname: missing operand' because it’s
> looking for jars associated with the oozie-client rpm instead of the
> versioned rpm as it passes the name to rpm -q on line 82 of
> /var/lib/ambari-agent/data/tmp/oozieSmoke2.sh
> The workaround is to edit line 82 of
> /var/lib/ambari-agent/data/tmp/oozieSmoke2.sh and replace 'ooze-client' with
> 'oozie_2_2_0_0_2041-client'.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
