You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2015/03/13 20:15:38 UTC
[jira] [Commented] (AMBARI-10055) RU failed on RESTART Oozie Server
because hadoop-lzo should only be copied if lzo compression is enabled
[ https://issues.apache.org/jira/browse/AMBARI-10055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14360955#comment-14360955 ]
Hadoop QA commented on AMBARI-10055:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12704482/AMBARI-10055.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 3 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/2023//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/2023//console
This message is automatically generated.
> RU failed on RESTART Oozie Server because hadoop-lzo should only be copied if lzo compression is enabled
> ---------------------------------------------------------------------------------------------------------
>
> Key: AMBARI-10055
> URL: https://issues.apache.org/jira/browse/AMBARI-10055
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.0.0
> Reporter: Alejandro Fernandez
> Assignee: Alejandro Fernandez
> Labels: rolling_upgrade
> Fix For: 2.0.0
>
> Attachments: AMBARI-10055.patch
>
>
> STR:
> Deploy a cluster with Oozie
> Confirm that lzo compression is not enabled ( http://docs.hortonworks.com/HDPDocuments/Ambari-1.6.0.0/bk_ambari_reference/content/ambari-ref-lzo-configure.html)
> Comment a Rolling Upgrade, which will fail in Oozie because it will not find the hadoop-lzo jar.
> The jar should only be copied if lzo is enabled.
> {code}
> 2015-03-11 21:32:49,019 - u"Execute['hdp-select set oozie-server 2.2.2.0-2591']" {}
> 2015-03-11 21:32:49,064 - Restoring Oozie configuration directory after upgrade...
> 2015-03-11 21:32:49,065 - Extracting /tmp/oozie-upgrade-backup/oozie-conf-backup.tar to /etc/oozie/conf
> 2015-03-11 21:32:49,179 - Error while executing command 'restart':
> Traceback (most recent call last):
> File "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py", line 214, in execute
> method(env)
> File "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py", line 365, in restart
> self.pre_rolling_restart(env)
> File "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_server.py", line 165, in pre_rolling_restart
> oozie_server_upgrade.prepare_libext_directory()
> File "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_server_upgrade.py", line 141, in prepare_libext_directory
> hadoop_client_new_lib_dir, hadoop_lzo_pattern))
> Fail: There are no files at /usr/hdp/2.2.2.0-2591/hadoop/lib matching hadoop-lzo*.jar
> 2015-03-11 21:32:49,235 - Command: /usr/bin/hdp-select status oozie-server > /tmp/tmpVfVrGL
> Output: oozie-server - 2.2.2.0-2591
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)