Comment 5 for bug 1964137

I'm debugging a dump of the openstack database generated with the command
mysqldump --databases nova

Database: nova
Table:compute_nodes

('2022-03-07 15:28:50', ... ,'catgpa01',1.5,16,'7727a631-86ba-4319-8bd3-f7e33dc0eb7a',1,1),
('2022-03-07 17:56:59', ... ,'catgpa01',1.5,16,'5b9853dc-a3be-466c-8ea2-2cea2e27d16c',1,1),
('2022-03-08 08:25:16', ... ,'catgpa01',1.5,16,'e224cb92-c659-4fed-81e9-5ce7ee2832fd',1,1);

Last line contains the "e224cb92-c659-4fed-81e9-5ce7ee2832fd" id listed in the error message that I got in the /var/log/nova/nova-api.log file;

2022-03-08 15:23:40.545 2569811 ERROR nova.api.openstack.wsgi [req-82511bfa-660d-41de-ab8a-c1b2dc78d623 d2fba82966a44a82b2624f75f65f9ad0 3de2426941b943fd95633b0dbaedfd3f - default default] Unexpected exception in API method: ValueError: No such provider e224cb92-c659-4fed-81e9-5ce7ee2832fd

Is it normal that "catgpa01" node is listed several times in nova.compute_nodes table?

Keep in mind that I added this node in the past and deleted it successfully with the command "openstack compute service delete 42"

but it does not coincide with the identifier 5b9853dc-a3be-466c-8ea2-2cea2e27d16c that
currently appears in the "placement" database:

Database: placement
Table:resource_providers

('2022-03-07 17:57:00',... ,17,'5b9853dc-a3be-466c-8ea2-2cea2e27d16c','catgpa01',6,17,NULL);

As you see... the placement database contains the id assigned the previous time I added the catgpa01 host (the previous day)

Have I found a bug?

Is it normal that a host appears several times in nova.compute_nodes database?

Is it normal that the id of a host in placement.resource_providers is not the last one of the appearances in nova.compute_nodes database?

It is safe to manually modify one of the databases to sync the values and then run the
«openstack compute service delete» command?