DB migrations is in a bad state

Bug #1862379 reported by Björn Tillenius
6
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/maasserver/migrations/maasserver/0202_auto_20200207_1516.py
    - Alter field node on event

Tracking it down, it looks like d593bba28ede53bc5215f65df02bbe8f2f72d0e3 introduce a DB migration without a corresponding change in the Python code.

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

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
Alberto Donato (ack)
Changed in maas:
milestone: none → 2.8.0b1
Alberto Donato (ack)
Changed in maas:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.