DB migrations is in a bad state
Bug #1862379 reported by
Björn Tillenius
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
High
|
Adam Collard | ||
2.7 |
Fix Released
|
Critical
|
Adam Collard |
Bug Description
The DB migrations in master (and 2.7) are in a bad state. If you try to generate them in a clean tree, you get this:
Migrations for 'maasserver':
src/maasserve
- Alter field node on event
Tracking it down, it looks like d593bba28ede53b
It looks like we want it like the Python code currently defines it. Commit
1252f885bd changed it to DO_NOTHING to make Node.delete() faster.
So we need to add a DB patch, rather than change the Python code.
Related branches
~adam-collard/maas:event-node-migration-donothing-2.7
- Alberto Donato (community): Approve
-
Diff: 30 lines (+24/-0)1 file modifiedsrc/maasserver/migrations/maasserver/0202_event_node_on_delete.py (+24/-0)
~adam-collard/maas:event-node-migration-donothing
Merged
into
maas:master
- MAAS Lander: Needs Fixing
- Alberto Donato (community): Approve
-
Diff: 30 lines (+24/-0)1 file modifiedsrc/maasserver/migrations/maasserver/0202_event_node_on_delete.py (+24/-0)
Changed in maas: | |
status: | New → Triaged |
importance: | Undecided → High |
Changed in maas: | |
milestone: | none → 2.7.0rc6 |
status: | Triaged → Fix Committed |
Changed in maas: | |
assignee: | nobody → Adam Collard (adam-collard) |
milestone: | 2.7.0rc6 → none |
status: | Fix Committed → In Progress |
Changed in maas: | |
status: | In Progress → Fix Committed |
Changed in maas: | |
milestone: | none → 2.8.0b1 |
Changed in maas: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.