ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-13017) Installing falcon with blueprint, oozie extensions are missing, hence causing misconfigured installations that are using blueprint
Date Fri, 18 Sep 2015 22:35:04 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-13017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14876605#comment-14876605
] 

Hadoop QA commented on AMBARI-13017:
------------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12761146/AMBARI-13017.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/3816//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/3816//console

This message is automatically generated.

> Installing falcon with blueprint, oozie extensions are missing, hence causing misconfigured
installations that are using blueprint
> ----------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-13017
>                 URL: https://issues.apache.org/jira/browse/AMBARI-13017
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.1.0
>         Environment: all
>            Reporter: Sandor Magyari
>            Assignee: Sandor Magyari
>            Priority: Critical
>             Fix For: 2.2.0
>
>         Attachments: AMBARI-13017.patch
>
>
> PROBLEM: Installing falcon with blueprint, oozie extensions are missing, hence causing
misconfigured installations that are using blueprint. 
> For instance, on the sandbox which uses blueprint to install falcon(attached to this
bug) outputs the following for 
> grep -i ext /etc/oozie/conf/oozie-site.xml
> <name>oozie.services.ext</name>
> on a cluster that install falcon via add service via the webui, running grep -i ext /etc/oozie/conf/oozie-site.xml
produces 
> <name>oozie.service.ELService.ext.functions.coord-action-create</name>
> <name>oozie.service.ELService.ext.functions.coord-sla-create</name>
> <name>oozie.service.ELService.ext.functions.coord-sla-submit</name>
> Hence, the blueprint install will be missing needed properties.
> IMPACT: falcon will not operate as expected
> STEPS TO REPRODUCE:
> 1. Install cluster via ambari blueprint attached. 
> 2. view the oozie site and do grep -i ext /etc/oozie/conf/oozie-site.xml
> 3. Install cluster via ambari webui UI 
> 4. view the oozie site and do grep -i ext /etc/oozie/conf/oozie-site.xml you should proper
complete set of configs.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message