You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2017/11/30 21:13:00 UTC
[jira] [Commented] (AMBARI-22568) Oozie Fails To Restart During
Upgrade Because of Missing ExtJS Library
[ https://issues.apache.org/jira/browse/AMBARI-22568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16273439#comment-16273439 ]
Hadoop QA commented on AMBARI-22568:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12900083/AMBARI-22568.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 release audit{color}. The applied patch does not increase the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the total number of javac compiler warnings.
{color:red}-1 core tests{color}. The test build failed in [ambari-server|https://builds.apache.org/job/Ambari-trunk-test-patch/12780//artifact/patch-work/testrun_ambari-server.txt]
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/12780//console
This message is automatically generated.
> Oozie Fails To Restart During Upgrade Because of Missing ExtJS Library
> ----------------------------------------------------------------------
>
> Key: AMBARI-22568
> URL: https://issues.apache.org/jira/browse/AMBARI-22568
> Project: Ambari
> Issue Type: Bug
> Affects Versions: 2.6.1
> Reporter: Jonathan Hurley
> Assignee: Jonathan Hurley
> Priority: Blocker
> Fix For: 2.6.1
>
> Attachments: AMBARI-22568.patch
>
>
> 1) Deployed cluster with Ambari version: 2.6.1.0-65 and HDP version: 2.6.3.0-215
> 2) Express upgrade to target version 2.6.4.0-52
> Oozie Server Restart fails with below error:
> {code:java}
> Traceback (most recent call last):
> File "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_server.py", line 150, in <module>
> OozieServer().execute()
> File "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py", line 367, in execute
> method(env)
> File "/usr/lib/python2.6/site-packages/resource_management/libraries/script/script.py", line 946, in restart
> self.pre_upgrade_restart(env, upgrade_type=upgrade_type)
> File "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_server.py", line 123, in pre_upgrade_restart
> OozieUpgrade.prepare_libext_directory(upgrade_type=upgrade_type)
> File "/var/lib/ambari-agent/cache/common-services/OOZIE/4.0.0.2.0/package/scripts/oozie_server_upgrade.py", line 113, in prepare_libext_directory
> raise Fail("Unable to find any Oozie source extension files from the following paths {0}".format(source_ext_zip_paths))
> resource_management.core.exceptions.Fail: Unable to find any Oozie source extension files from the following paths ['/usr/share/HDP-oozie/ext-2.2.zip', '/var/lib/oozie/ext-2.2.zip']
> {code}
> This is because we have removed the requirement of having ExtJS in the cluster.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)