[
https://issues.apache.org/jira/browse/AMBARI-14678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15101600#comment-15101600
]
Hadoop QA commented on AMBARI-14678:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12782425/AMBARI-14678.trunk.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 patch failed these unit tests in
ambari-server:
org.apache.ambari.server.state.UpgradeHelperTest
org.apache.ambari.server.controller.internal.UpgradeResourceProviderTest
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/4929//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/4929//console
This message is automatically generated.
> RU - Oozie HA, Service Check fails since the pre-upgrade directive has
> multiple tasks that should run only on the specified hosts
> ---------------------------------------------------------------------------------------------------------------------------------
>
> Key: AMBARI-14678
> URL: https://issues.apache.org/jira/browse/AMBARI-14678
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.2.0
> Reporter: Alejandro Fernandez
> Assignee: Alejandro Fernandez
> Fix For: 2.2.1
>
> Attachments: AMBARI-14678.trunk.patch
>
>
> STR:
> HDP 2.2
> Multiple Oozie Servers
> RU to HDP 2.3
> The pre-upgrade directive for Oozie has
> {code}
> <pre-upgrade>
> <task xsi:type="execute" hosts="all" summary="Shut down all Oozie servers">
> <script>scripts/oozie_server.py</script>
> <function>stop</function>
> </task>
> <task xsi:type="execute" hosts="any" summary="Upgrading the database and
> creating a new sharelib">
> <script>scripts/oozie_server_upgrade.py</script>
> <function>upgrade_oozie_database_and_sharelib</function>
> </task>
> </pre-upgrade>
> {code}
> Notice that the first task runs on all hosts, and the second task runs on
> exactly one random host. The problem is that the scheduler runs both tasks in
> one stage on the union of these hosts. Therefore, the 2nd task runs on the
> wrong set of hosts.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
