[jira] [Commented] (AMBARI-15490) DB connection check installs JDK with incorrect permissions. umask 027, non root

["Hadoop QA (JIRA)" <ji...@apache.org>]

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

Hadoop QA commented on AMBARI-15490:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12794508/AMBARI-15490.patch
  against trunk revision .

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

    {color:red}-1 tests included{color}.  The patch doesn't appear to include any new or modified tests.
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    {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/5946//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/5946//console

This message is automatically generated.

> DB connection check installs JDK with incorrect permissions. umask 027, non root
> --------------------------------------------------------------------------------
>
>                 Key: AMBARI-15490
>                 URL: https://issues.apache.org/jira/browse/AMBARI-15490
>             Project: Ambari
>          Issue Type: Bug
>            Reporter: Andrew Onischuk
>            Assignee: Andrew Onischuk
>             Fix For: 2.2.2
>
>         Attachments: AMBARI-15490.patch
>
>
> **STR**  
> 1) Setup umask 027, non root agent  
> 2) During the wizard set Oozie server and Ambari-server on different hosts  
> 3) On service configuration step set Oozie db as "Existing MySQL Database" and
> hit "Test Connection" button  
> 4) Deploy the cluster
> To reproduce this DB connection check should be executed before any host
> command (BEFORE-ANY hook setups JDK as well)
> **Result**  
> On the host with Oozie server (where DB connection check was executed) JDK is
> installed with incorrect permissions. Services will fail to start.
>     
>     
>     /usr/jdk64/jdk1.8.0_60/bin/java: error while loading shared libraries: libjli.so: cannot open shared object file: No such file or directory
>     
>     [root@c6406 ~]# ll /usr/jdk64/jdk1.8.0_60/jre/lib/amd64/jli/libjli.so
>     -rwxr-x--- 1 vagrant vagrant 102352 Aug  4  2015 /usr/jdk64/jdk1.8.0_60/jre/lib/amd64/jli/libjli.so
>     [root@c6406 ~]# ll /usr/jdk64/jdk1.8.0_60/lib/amd64/jli/libjli.so
>     -rwxr-x--- 1 vagrant vagrant 102990 Aug  4  2015 /usr/jdk64/jdk1.8.0_60/lib/amd64/jli/libjli.so
>     



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