Comment 1 for bug 1834500

Per Jay's findings, current workaround involves DB surgery below:

How to reset state in the maasdb database (to 'Deployed')

On the maas machine:

sudo maas-region dbshell

-- find node system_id (get it from maas UI, at the end of the url: #/node/xxxxxx)
-- find owner_id (for maas-root, or main maas user if maas-root is incorrect) - easiest way is to find a working machine that is owned by that user also:

maasdb=# select id, system_id, owner_id, hostname, status, previous_status, power_state from maasserver_node where hostname='myworkingmachine';

-- assuming your owner_id is 3, and your system_id of your broken machine is 'xyzpd4'

update maasserver_node set owner_id=3, status=6 where system_id='xyzpd4';

-- this will put your machine back in the correct status and with the correct owner. (Owner will be wiped on the previous transition to READY, it seems)