installworker fails to set LAVA_DB_SERVER variable

Bug #1266901 reported by Alan Bennett
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
LAVA Deployment Tool
Fix Released
High
Neil Williams

Bug Description

Install new worker
  - LAVA_DB_PASSWORD=lava123 LAVA_MASTER=lavaservername ./lava-deployment-tool installworker productionssss -n

Check for the Server name in the instance.conf
  - grep LAVA_DB_SERVER /srv/lava/instances/productionssss/instance.conf
     LAVA_DB_SERVER=""

Alan Bennett (akbennett)
Changed in lava-deployment-tool:
importance: Undecided → High
status: New → Triaged
assignee: nobody → Neil Williams (codehelp)
Revision history for this message
Neil Williams (codehelp) wrote :

In the example from the description, was the postgres database intended to be accessible from the remote worker at the location "lavaservername" ?

If support is needed for postgres installations separate from the main server running Apache, then a new default value would be needed.

Revision history for this message
Alan Bennett (akbennett) wrote :

I agree. Currently l-d-t remoteworker installations assume the DB resides on the LAVA_MASTER.

We should use (and document) a variable, such as LAVA_DB_MASTER to allow a installer to identify a specific DB Server address.

If that environment variable is not set, we then use the LAVA_MASTER (as we do today, maintaining backwards-compatibility)

Revision history for this message
Neil Williams (codehelp) wrote :

Change available for review: https://review.linaro.org/#/c/872/

Neil Williams (codehelp)
Changed in lava-deployment-tool:
status: Triaged → In Progress
Neil Williams (codehelp)
Changed in lava-deployment-tool:
status: In Progress → Fix Committed
Changed in lava-deployment-tool:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.