-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
2025.1 (Upstream E)
-
None
-
False
-
-
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
- is related to
-
OSPRH-13064 Provide a workaround for NVMe disk cleanup in 18.0
-
- Closed
-