Hello Melanie,

Thank you for your reply. It seems that everything is OK right now, after applying a patch I can see:
# placement-status upgrade check
+----------------------------------+
| Upgrade Check Results            |
+----------------------------------+
| Check: Missing Root Provider IDs |
| Result: Success                  |
| Details: None                    |
+----------------------------------+
| Check: Incomplete Consumers      |
| Result: Success                  |
| Details: None                    |
+----------------------------------+
I've seen that zuul added -1 to review for this check, however I will apply my internal patch for it, additionally that you mentioned that such orphaned records shouldn't hurt me. Once again - thank you for your help.

Best regards,
Jan

czw., 5 maj 2022 o 19:05 melanie witt <melwittt@gmail.com> napisał(a):
On Thu May 05 2022 09:58:10 GMT-0700 (Pacific Daylight Time), melanie
witt <melwittt@gmail.com> wrote:
> You may still have orphaned consumers table records in the placement
> database but they don't hurt anything. If you want/need to clean them
> up, it has to be done manually, something like (disclaimer I did not
> test this):
>
> delete from placement.consumers where placement.consumers.uuid not in
> (select nova_api.instance_mappings.instance_uuid from
> nova_api.instance_mappings where
> nova_api.instance_mappings.queued_for_delete = true);

Sorry I got the where condition backwards, it should be:

delete from placement.consumers where placement.consumers.uuid not in
(select nova_api.instance_mappings.instance_uuid from
nova_api.instance_mappings where
nova_api.instance_mappings.queued_for_delete != true);

And you might have s/placement/nova_api/ if you did not break out the
separate placement database.

-melanie