Le mer. 30 juin 2021 à 11:31, Balazs Gibizer <balazs.gibizer@est.tech> a écrit :
On Tue, Jun 29, 2021 at 20:42, Jeffrey Mazzone <jmazzone@uchicago.edu>
wrote:
> Hello,
>
>
[snip]
> Trying to start another vm on that host fails with the following log
> entries:
>
> scheduler.log
>
> "status": 409, "title": "Conflict", "detail": "There was a conflict
> when trying to complete your request.\n\n Unable to allocate
> inventory: Unable to create allocation for 'VCPU' on resource provider
>
> conductor.log
>
> Failed to schedule instances:
> nova.exception_Remote.NoValidHost_Remote: No valid host was found.
> There are not enough hosts available.
>
> placement.log
>
> Over capacity for VCPU on resource provider
> 3f9d0deb-936c-474a-bdee-d3df049f073d. Needed: 4, Used: 8206,
> Capacity: 1024.0
At this point if you list the resource provider usage on
3f9d0deb-936c-474a-bdee-d3df049f073d again then do you still see 4 VCPU
used, or 8206 used? With the "openstack resource provider show
3f9d0deb-936c-474a-bdee-d3df049f073d --allocations" command you could
print the UUIDs of the consumers that are actually consuming your VCPUs
in placement. So you can try to identify where the 8206 allocation is
coming from.
Given you also have an Ussuri deployment, you could call the nova-audit command to see whether you would have orphaned allocations :
nova-manage placement audit [--verbose] [--delete] [--resource_provider <uuid>]
-Sylvain
Cheers,
gibi
>
> As you can see, the used value is suddenly 8206 after a single 4 core
> vm is placed on it. I don’t understand what im missing or could be
> doing wrong. Im really unsure where this value is being calculated
> from. All the entries in the database and via openstack commands show
> the correct values except in this log entry. Has anyone experienced
> the same or similar behavior? I would appreciate any insight as to
> what the issue could be.
>
> Thanks in advance!
>
> -Jeff M
>
>
>
>