Closed
Bug 966092
Opened 11 years ago
Closed 8 years ago
graphs data.sql is no longer reliable
Categories
(Release Engineering :: General, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: mozilla, Unassigned)
Details
(Whiteboard: [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/3292] )
The theory behind a sql file like this is you can run it against an empty database and get an equivalent production schema.
We have inserted new lines out of order, and branch names in the file don't represent branch names in the database. Staging is out of sync with production, as well. I think we have to start over.
Ideally we retire graphserver before we have to solve this, but I'm not sure how reliable that would be.
One way to solve this without a ton of human intervention would be to dump the applicable schemas + branches/machines tables from production to a new data.sql file, and check that in. Then blow away staging graphs and copy over production, and voila, we're in sync again.
Updated•10 years ago
|
Whiteboard: [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/3282]
Updated•10 years ago
|
Whiteboard: [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/3282] → [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/3287]
Updated•10 years ago
|
Whiteboard: [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/3287] → [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/3292]
Comment 1•8 years ago
|
||
graph server is dead
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
Assignee | ||
Updated•7 years ago
|
Component: General Automation → General
You need to log in
before you can comment on or make changes to this bug.
Description
•