launchpad.conf should support alternative port for database connection

Bug #2064 reported by Matthew Paul Thomas
14
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
Low
Stuart Bishop

Bug Description

launchpad.conf allows specification of the dbname and dbhost, but not of the port to connect to that host. This causes a failure if (as in my case) PGPORT defaults to some port other than 5431.

Workaround: PGPORT= make run

Dafydd Harries (daf)
Changed in launchpad:
assignee: nobody → stub
status: New → Accepted
Revision history for this message
Stuart Bishop (stub) wrote :

Other work around is to reconfigure PostgreSQL to listen on the standard port.

Changed in launchpad:
importance: Medium → Wishlist
Revision history for this message
Tom Haddon (mthaddon) wrote :

The workaround is current broken too. I'm marking as critical because this is a blocker for hardy PQM chroot.

https://pastebin.canonical.com/5209/ is the error we're getting, which according to Kiko is related to the following in portforward-to-postgres.tac:

pf = portforward.ProxyFactory(dbhost, 5432)

This should look for an environment variable of PGPORT, and use that, or default to 5432.

Changed in launchpad:
importance: Wishlist → Critical
Revision history for this message
Tom Haddon (mthaddon) wrote :

Branch on its way to PQM that will restore the workaround to working order. Will revert to "wishlist" once it's landed.

Revision history for this message
Tom Haddon (mthaddon) wrote :

PGPORT workaround fix committed to RF in revno 6292.

Changed in launchpad:
importance: Critical → Wishlist
Stuart Bishop (stub)
Changed in launchpad-foundations:
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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