Uploaded image for project: 'Red Hat OpenStack Services on OpenShift'
  1. Red Hat OpenStack Services on OpenShift
  2. OSPRH-14164

Updating reserved value of an inventory created by Nova is undefined behavior

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • 2025.1 (Upstream E)
    • openstack-nova
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • ?
    • None
    • Compute Next Sprint Candidates
    • 1
    • Moderate

      There is no upstream or downstream documentation about what are Nova's expectation about placement inventories it creates. Is it allowed to update the reserved field via the Placement API? Or will it be always overwritten by Nova?

      Expected behavior

      • have a clear definition of the expected behavior or Nova regarding the reserved field
      • have test cases proving the behavior

      Bug impact

      • current situation can cause misunderstanding about the possible usage of the Placement API

      Known workaround

      • None

      Additional context

      • Based on my local testing Nova does not override the reserved value on PCI resource providers

       

              rh-ee-bgibizer Balazs Gibizer
              rh-ee-bgibizer Balazs Gibizer
              rhos-dfg-compute
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: