soyuz is not fast-downtime friendly

Bug #845407 reported by Tom Haddon on 2011-09-09
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Launchpad itself

Bug Description

Soyuz cannot currently cope with fastdowntime, which means a lot of workarounds to allow us to do fastdowntime:

- Disabe notifications of soyuz services in nagios
- Stop individual cron jobs to prevent them being long running
- Stop soyuz services before rollout
- Stop all soyuz crontabs before rollout
- Bring soyuz services back up after rollout
- Re-enable crontabs after rollout
- Re-enable nagios alerts after rollout

The idea of fastdowntime is that we shouldn't have to do any of these, which will make the process less error prone and quicker

Tom Haddon (mthaddon) on 2011-09-09
tags: added: canonical-losa-lp fastdowntime
Changed in launchpad:
importance: Undecided → High
Stuart Bishop (stub) wrote :

Last step of this is to remove archive-publisher from the fragile users list in database/schema/

Changed in launchpad:
status: New → Triaged
Tom Haddon (mthaddon) wrote :

process-death-row needed manual killing during today's rollout

Tom Haddon (mthaddon) wrote :

And buildd-retry-depwait on cesium.

Stuart Bishop (stub) wrote :

Bug #845397 is about making buildd-manager cope gracefully.

Stuart Bishop (stub) wrote :

Bug #815753 is about making scripts like process-death-row and buildd-retry-depwait connect as distinct database users, so they can be differentiated from other connections.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers