[
https://issues.apache.org/jira/browse/AMBARI-15490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15204512#comment-15204512
]
Andrew Onischuk commented on AMBARI-15490:
------------------------------------------
This failure doesn't look related to the change. It even completed the tests
the first time. I'm going to commit as is.
Run the tests manually:
{noformat}
[INFO] Rat check: Summary of files. Unapproved: 0 unknown: 0 generated: 0
approved: 141 licence.
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] Ambari Views ...................................... SUCCESS [2.946s]
[INFO] Ambari Metrics Common ............................. SUCCESS [0.826s]
[INFO] Ambari Server ..................................... SUCCESS [1:09.868s]
[INFO] Ambari Agent ...................................... SUCCESS [9.697s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1:27.130s
[INFO] Finished at: Mon Mar 21 17:57:33 EET 2016
[INFO] Final Memory: 71M/1382M
[INFO] ------------------------------------------------------------------------
{noformat}
> 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)
