Rob said: "I'd also like to note that we should include the OOPS in the 503 page (but very small, in a corner, or even just in the source)".
Thanks for that Rob. Yellow squad, could you put "(OOPS 123456)" directly after "...because our database has gone offline." please? Huw, if you have a better suggestion then please update your branch and let us know in a comment here. -- 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
