soyuz is not fast-downtime friendly
Bug #845407 reported by
Tom Haddon
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Triaged
|
High
|
Unassigned | ||
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
| tags: | added: canonical-losa-lp fastdowntime |
| Changed in launchpad: | |
| importance: | Undecided → High |
Revision history for this message
| Stuart Bishop (stub) wrote | #1 |
| Changed in launchpad: | |
| status: | New → Triaged |
Revision history for this message
| Tom Haddon (mthaddon) wrote | #2 |
Revision history for this message
| Tom Haddon (mthaddon) wrote | #3 |
Revision history for this message
| Stuart Bishop (stub) wrote | #4 |
Revision history for this message
| Stuart Bishop (stub) wrote | #5 |
To post a comment you must log in.
Last step of this is to remove archive-publisher from the fragile users list in database/