when qastaging is down deployment reports crash and stop updating
Bug #688082 reported by
Aaron Bentley
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
qa-tagger |
Triaged
|
High
|
Unassigned |
Bug Description
qa-tagger requires staging and qastaging to be running in order to determine which revno is deployed.
When this fails no fallback is present and the reports simply stop.
The deployment report is the best place to monitor QA status, so the release manager's job becomes harder when the report stops updating.
Solutions
=========
One possible fix would be to cache the last seen revnos and use those when the system cannot be queried (and show that it could not be queried in the UI).
Don't delete the old report if the new one fails to render.
summary: |
- Deployment reports are not updated if qastaging is down + when qastaging is down deployment reports crash and stop updating |
description: | updated |
Changed in qa-tagger: | |
status: | New → Triaged |
importance: | Undecided → High |
description: | updated |
tags: | added: easy |
To post a comment you must log in.