In case anyone needs a workaround before the final fix for this, I want to point out that this only affects the upgrade path if there are nodes in READY state. Therefore, a possible workaround is:
"sudo maas-region-admin dbshell"
followed by
"update maasserver_node set status=8 where status=4;"
This process will mark any READY nodes BROKEN. It's likely that nodes will need to be recommissioned after doing this before they can be deployed.
In case anyone needs a workaround before the final fix for this, I want to point out that this only affects the upgrade path if there are nodes in READY state. Therefore, a possible workaround is:
"sudo maas-region-admin dbshell"
followed by
"update maasserver_node set status=8 where status=4;"
This process will mark any READY nodes BROKEN. It's likely that nodes will need to be recommissioned after doing this before they can be deployed.