OpenStack Compute (nova)

  1. Bug #1710141
  2. Comment #7

Comment 7 for bug 1710141

Revision history for this message
Mark Goddard (mgoddard) wrote :

I think we're seeing a similar issue to this on Pike with this fix applied. We have resource providers for active ironic nodes that have no inventory in placement. When the resource tracker tries to update the RP allocations, we get a conflict because there is no inventory to allocate from for the RP:

Unable to submit allocation for instance 5073a390-6c10-4b1b-a097-f9f67485463c (409 <html>
 <head>
  <title>409 Conflict</title>
 </head>
 <body>
  <h1>409 Conflict</h1>
  There was a conflict when trying to complete your request.<br /><br />
Unable to allocate inventory: Inventory for 'VCPU, MEMORY_MB, DISK_GB, CUSTOM_CUSTOM_B' on resource provider '2ce4ab0c-0d8b-4ae2-b84d-4bbc1888df52' invalid.
 </body>
</html>)

It's likely that at some point the original RPs for the ironic nodes were deleted - due to https://bugs.launchpad.net/nova/+bug/1714248.

It seems that the inventory is not reported to the resource tracker since the fix for https://bugs.launchpad.net/nova/+bug/1723423 was merged, as it reports no inventory when the node is unavailable (note the TODO [1]).

Environment: CentOS 7.4 kolla containers, RDO python-nova-16.0.3-2.el7.noarch.

[1] https://github.com/openstack/nova/blob/d25feca/nova/virt/ironic/driver.py#L758