Trying to delete a region/rack that no longer exists, results in {'pool': ["Can't assign to a resource pool."]}

Bug #1774538 reported by james beedy
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Fix Released
Critical
Alberto Donato
2.4
Fix Released
Critical
Alberto Donato

Bug Description

The situation is such that I killed off an old 2.3 region+rack controller, installed 2.4 region+rack on a new bionic box, migrated the db and pointed my new 2.4 deploy at the now migrated db.

Everything went pretty smooth, except that my old 2.3 region controller won't leave the database.

When I try to remove the old 2.3 region+rack controller via cli/gui I get this error:
"{'pool': ["Can't assign to a resource pool."]}"

regiond.log: http://paste.ubuntu.com/p/wNCy8c4n2c/

gui: https://imgur.com/a/yitXnRk

Related branches

Changed in maas:
importance: Undecided → Critical
milestone: none → 2.4.1
milestone: 2.4.1 → 2.5.0
status: New → Triaged
tags: added: resource-pools
james beedy (jamesbeedy)
description: updated
Alberto Donato (ack)
Changed in maas:
assignee: nobody → Alberto Donato (ack)
Alberto Donato (ack)
Changed in maas:
status: Triaged → In Progress
Changed in maas:
status: In Progress → Fix Committed
Changed in maas:
milestone: 2.5.0 → 2.5.0alpha1
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.