full-update.py too picky about long running transactions
Bug #844616 reported by
Stuart Bishop
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Fix Released
|
High
|
Stuart Bishop | ||
Bug Description
full-update.py refused to proceed because a cronscript was running that holds transactions open for too long (update-pkg-cache). We should not block in this case.
| Changed in launchpad: | |
| status: | New → Triaged |
| importance: | Undecided → High |
| assignee: | nobody → Stuart Bishop (stub) |
| tags: | added: fastdowntime-later |
Revision history for this message
| Stuart Bishop (stub) wrote | #1 |
Revision history for this message
| Stuart Bishop (stub) wrote | #2 |
Revision history for this message
| Launchpad QA Bot (lpqabot) wrote | #4 |
| tags: | added: qa-needstesting |
| Changed in launchpad: | |
| status: | Triaged → Fix Committed |
| tags: |
added: qa-ok removed: qa-needstesting |
| Changed in launchpad: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Current threshold is 10s, which is too low. Bumping it up to 60 seconds.
We still want the check, as long running transactions are symptoms or problems and indicate things are not healthy. We should not attempt rollouts when the system is not healthy.