The assert I mentioned in comment #2 should probably go. I think it was added to track down disconnection errors we were seeing (and have now been fixed in Storm).
http://bazaar.launchpad.net/~launchpad- pqm/launchpad/devel/view/head:/lib/canonical/librarian/tests/test_db_outage.py has tests for how the Librarian handles an outage. A similar approach should be doable to bring up an appserver connected via pgbouncer. If it is a problem, I was toying with the idea of installing the pgbouncer fixture once for everything and running all tests through it. -- You received this bug notification because you are a member of Launchpad Yellow Squad, which is a bug assignee. https://bugs.launchpad.net/bugs/844631 Title: Launchpad should return 503 error pages when database is unavailable Status in Launchpad itself: Triaged Bug description: When a PostgreSQL database is unavailable, we should return a 503 error code instead of a 500. We should still log an OOPS. We can make the page pretty. Wording might be tricky, as Launchpad will not know if this was a scheduled outage or if a power cord has been kicked out. To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad/+bug/844631/+subscriptions -- Mailing list: https://launchpad.net/~yellow Post to : [email protected] Unsubscribe : https://launchpad.net/~yellow More help : https://help.launchpad.net/ListHelp
