[ https://issues.apache.org/jira/browse/AMBARI-24916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16692930#comment-16692930 ]
Viraj Jasani commented on AMBARI-24916: --------------------------------------- Fair enough. At this point, separating setup for JDBC as another command might cause regression for Automation scripts. [~adoroszlai] Should we go ahead and remove second JDBC check condition as part of this JIRA? > Ambari Server setup for non embedded DB miss out on default configuration > ------------------------------------------------------------------------- > > Key: AMBARI-24916 > URL: https://issues.apache.org/jira/browse/AMBARI-24916 > Project: Ambari > Issue Type: Bug > Components: ambari-server > Affects Versions: 3.0.0, 2.6.0, 2.6.1, 2.6.2, 2.7.0, 2.7.1, 2.7.2 > Reporter: Viraj Jasani > Priority: Critical > Fix For: 3.0.0, 2.6.0, 2.6.1, 2.6.2, 2.7.0, 2.7.1, 2.7.2 > > > If we setup Ambari Server with it's own embedded postgresql DB, we get all > other configurations correctly e.g. setup command updates home.java, > server.os_type, server.os_family etc in ambari.properties file that can be > used during starting Ambari Server. > > However, if we provide server setup command with arguments to use > non-embedded standalone DB, server setup does not update ambari.properties > and does not perform any further setup utility that can be leveraged during > starting Ambari Server. > Example: > 1) *ambari-server setup -j \{JDK_PATH} -s* > This command updates ambari.properties for home.java, server.os_type, > server.os_family etc. > > 2) *ambari-server setup --java-home=\{JDK_PATH} --jdbc-db=postgres > --jdbc-driver=\{JDBC_DRIVER_PATH} --databasehost=\{IP_ADDR} > --databaseport=5432 --databasename=ambari --postgresschema=ambari > --databaseusername=\{DB_USER} --databasepassword=\{DB_PASSWD} > --database=postgres -s* > This command does not update ambari.properties and we need to update it > manually to bring up Ambari Server. Hence, automation of server setup with > server startup is blocked due to this bug. -- This message was sent by Atlassian JIRA (v7.6.3#76005)