Comment 0 for bug 1774538

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 api/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