Instance has allocations against this compute host but is not found in the database

Products

• VMware Integrated OpenStack

Issue/Introduction

• Instances are erroring on creation
• The nova compute log(s) show a message similar to below:
  2025-11-10 08:29:47.397 1 INFO nova.compute.resource_tracker [req-########-####-####-####-############ - - - - -] Instance ########-####-####-####-############ has allocations against this compute host but is not found in the database.
• Testing workload placement with this command returns no resource providers
  #openstack allocation candidate list --os-placement-api-version 1.10 --resource VCPU=1 --resource MEMORY_MB=2048 --resource DISK_GB=20

Environment

7.x

Cause

The message in the logs indicate that there are orphaned resource allocations in the placement service which can cause resource providers to:

• Appear to the scheduler to be more utilized than they really are

• Prevent deletion of compute services

Resolution

Workaround: 

1. Use this kb Change VM resource allocation ratios to determine which resource (CPU, RAM, Disk) is causing a problem.  
2. Change the appropriate allocation ratio (CPU, RAM, Disk) to allow more over-commit of resource.
3. Contact Broadcom support to determine a proper course of action for cleanup of these orphaned resource allocations.

Additional Information

Note:  Make sure the following are uploaded to the SR

1. Collect a support bundle from the deployment 
2. Collect nova database and placement database for review.
   

   #osctl exec -it mariadb-server-0 bash
mysqldump --defaults-file=/etc/mysql/admin_user.cnf --host=localhost <database> > /tmp/<database>.sql
exit

   #osctl cp openstack/mariadb-server-0:/tmp/<database>.sql /tmp/<database>.sql

   Then you just pull the backup from the manager.  Something like winscp

   Note:  We will need the following 3 databases:
   nova, nova_api, placement

Orphaned resource allocations