Hadoop QA commented on AMBARI-18546:

{color:green}+1 overall{color}.  Here are the results of testing the latest 
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author 

    {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 

Test results: 
Console output: 

This message is automatically generated.

> BP format does not generate property oozie.service.JPAService.jdbc.url
> ----------------------------------------------------------------------
>                 Key: AMBARI-18546
>                 URL: https://issues.apache.org/jira/browse/AMBARI-18546
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.4.0
>            Reporter: Vitaly Brodetskyi
>            Assignee: Vitaly Brodetskyi
>            Priority: Critical
>             Fix For: 2.5.0
>         Attachments: AMBARI-18546.patch, AMBARI-18546_part2.patch
> STR:
> * Install Ambari with HDP 2.5 and Oozie (using existing MySQL DB).
> * Notice that oozie-site has config,
> {code}
> oozie.service.JPAService.jdbc.url=jdbc:mysql://$SERVER/$oozie.db.schema.name
> {code}
> E.g.,
> jdbc:mysql://c6401.ambari.apache.org/oozie
> * Export the BP,
> api/v1/clusters/c1?format=blueprint
> It doesn't generate the "oozie.service.JPAService.jdbc.url" property, so a 
> user trying to use that blueprint will run into errors.
> Further, setting the value of that property to 
> "jdbc:mysql://%HOSTGROUP::host_group_1%/oozie" does not actually replace it 
> with the hostname, and it should also dynamically replace the Oozie DB name.

This message was sent by Atlassian JIRA

Reply via email to