I went scorched earth on the database and it seems to have fixed it. As soon as I deleted
the transfer the HA launched the VM. Hopefully this helps others.
[root@kvmo-el8 ~]# su - postgres
Last login: Sat Jul 8 04:53:32 EDT 2023 on pts/0
[postgres@kvmo-el8 ~]$ psql -U engine -W -h localhost -p 5432
Password:
psql (12.12)
Type "help" for help.
engine=> SELECT command_id,disk_id,last_updated, message,timeout_policy,type,active
FROM image_transfers;
command_id | disk_id |
last_updated | message | timeout_policy | type | active
--------------------------------------+--------------------------------------+----------------------------+---------+----------------+------+--------
5e8b4b53-1b14-499c-b1fb-f47ddb561c85 | | 2023-07-03
10:12:04.009-04 | | legacy | 1 | f
57bdaf89-414b-4431-bcfb-4ecb8b94d209 | | 2023-07-03
10:12:19.08-04 | | legacy | 1 | f
26a04e2e-23dc-4db8-9289-e91ad06fa0ee | | 2023-07-03
10:12:48.493-04 | | legacy | 1 | f
19bb57ac-0d16-4f0f-aa4d-a5b1a6c8c54d | | 2023-07-03
10:12:32.543-04 | | legacy | 1 | f
3b64e0ef-6bd2-49d2-a4ed-58c5926d77e3 | 086cc911-a584-43a8-b620-61fdd08be9f4 | 2023-07-08
05:15:44.877-04 | | legacy | 1 | f
(5 rows)
engine=> delete from image_transfers where
command_id='5e8b4b53-1b14-499c-b1fb-f47ddb561c85';
DELETE 1
engine=> delete from image_transfers where
command_id='57bdaf89-414b-4431-bcfb-4ecb8b94d209';
DELETE 1
engine=> delete from image_transfers where
command_id='26a04e2e-23dc-4db8-9289-e91ad06fa0ee';
DELETE 1
engine=> delete from image_transfers where
command_id='19bb57ac-0d16-4f0f-aa4d-a5b1a6c8c54d';
DELETE 1
engine=> SELECT command_id,disk_id,last_updated, message,timeout_policy,type,active
FROM image_transfers;
command_id | disk_id | last_updated | message | timeout_policy | type | active
------------+---------+--------------+---------+----------------+------+--------
(0 rows)
engine=>