[
https://issues.apache.org/jira/browse/AMBARI-9491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14307537#comment-14307537
]
Hadoop QA commented on AMBARI-9491:
-----------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12696776/AMBARI-9491.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 1 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/1597//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/1597//console
This message is automatically generated.
> Oozie Symlink Does Not Need To Be Removed During Upgrade
> --------------------------------------------------------
>
> Key: AMBARI-9491
> URL: https://issues.apache.org/jira/browse/AMBARI-9491
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
> Affects Versions: 2.0.0
> Reporter: Jonathan Hurley
> Assignee: Jonathan Hurley
> Priority: Critical
> Fix For: 2.0.0
>
> Attachments: AMBARI-9491.patch
>
>
> During the Oozie upgrade, we were instructed to remove the oozie symlink
> located at {{/usr/bin/oozie}}. This is actually not correct when upgrading
> from HDP 2.2 and results in the oozie command not being found on the path of
> upgraded hosts.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
