ambari-issues 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-20532) Ambari-server CLI to setup Database Options Broken
Date Tue, 28 Mar 2017 17:36:41 GMT

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

Hadoop QA commented on AMBARI-20532:
------------------------------------

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

This message is automatically generated.

> Ambari-server CLI to setup Database Options Broken
> --------------------------------------------------
>
>                 Key: AMBARI-20532
>                 URL: https://issues.apache.org/jira/browse/AMBARI-20532
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.4.2
>         Environment: Testing
>            Reporter: David Streever
>            Assignee: Dmytro Sen
>            Priority: Critical
>         Attachments: AMBARI-20532_2.patch
>
>
> When trying to automate the configuration of Ambari through the 'ambari-server setup'
with options to setup the database and JDK, the return claims success but fails to make adjustments
to 'ambari.properties' and 'password.dat' files.
> Example CLI Call:
> /usr/sbin/ambari-server setup --java-home=/usr/java/default --database=mysql --databasehost="db.hdp.local"
--databaseport=3306 --databasename=ambari --databaseusername=ambari --databasepassword=hortonworks
--jdbc-driver=/usr/share/java/mysql-connector-java.jar --jdbc-db=mysql --master-key=hortonworks
--master-key-persist=true --truststore-type=jceks --truststore-path=/etc/ambari-server/conf/password.jceks
--truststore-password=hortonworks -v -g



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message