To clarify why I consider this bug Critical: Our daily fast down-time is a great boost to the speed of getting new db-change-reliant features released. It has also got rid of that awful 90 minute window where parts of LP were down and other were read-only.
However, it has given us a user-experience regression in that we now present an OOPS rather than a friendlier "Hey, Launchpad is read-only but you can still do some stuff" message. In my view: * an unexplained OOPS for up to five minutes a day, potentially every day, just looks awful and I think it's safe to say that most people seeing the OOPS won't have read the blog nor will they have found out through our stakeholder process * Huw's new design brings in updates from the status feed and sends people to subscribe to that, thereby making us appear more reliable in future as they'll have had warning of such down-time. -- 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
