[AMBARI-24916] Ambari Server setup for non embedded DB miss out on default configuration

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 3.0.0, 2.6.0, 2.6.1, 2.6.2, 2.7.0, 2.7.1, 2.7.2
• Fix Version/s: 2.8.0
• Component/s: ambari-server
• Labels: pull-request-available
• Assignee: Attila Doroszlai
• Reporter: Viraj Jasani
• Created: 19/Nov/18 06:59
• Updated: 26/Feb/19 17:52
• Resolved: 21/Nov/18 06:42

Description

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.

Issue Links

• links to: GitHub Pull Request #2634

Sub-Tasks

• Backport AMBARI-24916 to branch-2.7: Open