[jira] [Commented] (AMBARI-15390) Ambari names jar 'ojdbc6.jar' even though it is actually ojdbc7.jar

2016-03-15 Thread Hudson (JIRA) 

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

Hudson commented on AMBARI-15390:
-

SUCCESS: Integrated in Ambari-trunk-Commit #4497 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/4497/])
AMBARI-15390. Test fix.Ambari names jar "ojdbc6.jar" even though it is 
(vbrodetskyi: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=dfe66f6907c7bd04aaa5e8a3a45a52de70e700dc])
* 
ambari-server/src/test/java/org/apache/ambari/server/controller/AmbariManagementControllerImplTest.java


> Ambari names jar 'ojdbc6.jar' even though it is actually ojdbc7.jar
> ---
>
> Key: AMBARI-15390
> URL: https://issues.apache.org/jira/browse/AMBARI-15390
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.1.2
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-15390.patch
>
>
> PROBLEM:
> When set up jdbc driver with 
> ambari-server setup --jdbc-db=oracle --jdbc-driver=/tmp/ojdbc7.jar
> and see that it is properly set up in /var/lib/ambari-server/resources, and 
> also cleaned up any ojdbc*.jar in the cluster, when restart HDFS service, 
> Ambari copies the jar but name it 'ojdbc6.jar'



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

[jira] [Commented] (AMBARI-15390) Ambari names jar 'ojdbc6.jar' even though it is actually ojdbc7.jar

2016-03-14 Thread Hudson (JIRA) 

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

Hudson commented on AMBARI-15390:
-

FAILURE: Integrated in Ambari-trunk-Commit #4490 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/4490/])
AMBARI-15390. Additional fix.Ambari names jar "ojdbc6.jar" even though 
(vbrodetskyi: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=c341a0f59f1ee4b630afe37c1b415cfc8e972827])
* 
ambari-server/src/main/java/org/apache/ambari/server/configuration/Configuration.java


> Ambari names jar 'ojdbc6.jar' even though it is actually ojdbc7.jar
> ---
>
> Key: AMBARI-15390
> URL: https://issues.apache.org/jira/browse/AMBARI-15390
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.1.2
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-15390.patch
>
>
> PROBLEM:
> When set up jdbc driver with 
> ambari-server setup --jdbc-db=oracle --jdbc-driver=/tmp/ojdbc7.jar
> and see that it is properly set up in /var/lib/ambari-server/resources, and 
> also cleaned up any ojdbc*.jar in the cluster, when restart HDFS service, 
> Ambari copies the jar but name it 'ojdbc6.jar'



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

[jira] [Commented] (AMBARI-15390) Ambari names jar 'ojdbc6.jar' even though it is actually ojdbc7.jar

2016-03-11 Thread Hadoop QA (JIRA) 

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

Hadoop QA commented on AMBARI-15390:


{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12792869/AMBARI-15390.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 9 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.controller.AmbariManagementControllerImplTest

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/5831//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/5831//console

This message is automatically generated.

> Ambari names jar 'ojdbc6.jar' even though it is actually ojdbc7.jar
> ---
>
> Key: AMBARI-15390
> URL: https://issues.apache.org/jira/browse/AMBARI-15390
> Project: Ambari
>  Issue Type: Bug
>  Components: ambari-server
>Affects Versions: 2.1.2
>Reporter: Vitaly Brodetskyi
>Assignee: Vitaly Brodetskyi
>Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-15390.patch
>
>
> PROBLEM:
> When set up jdbc driver with 
> ambari-server setup --jdbc-db=oracle --jdbc-driver=/tmp/ojdbc7.jar
> and see that it is properly set up in /var/lib/ambari-server/resources, and 
> also cleaned up any ojdbc*.jar in the cluster, when restart HDFS service, 
> Ambari copies the jar but name it 'ojdbc6.jar'



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