Commit graph

3 commits

Author SHA1 Message Date
Sunyanan Choochotkaew
801de96635
DRA: ConsumableCapacity update allocating and registry test cases
Signed-off-by: Sunyanan Choochotkaew <sunyanan.choochotkaew1@ibm.com>
2025-11-06 09:19:19 +09:00
Sunyanan Choochotkaew
4acafd9245
[DRA] Fix unexpected errors on ResourceClaim strategy update
- Fix setting distinctAttribute=nil when DRAConsumableCapacity is disabled
- Add must have no error check when no error expected in strategy test
- Update test case that causes unexpected errors

Signed-off-by: Sunyanan Choochotkaew <sunyanan.choochotkaew1@ibm.com>
2025-11-05 08:45:51 +09:00
Patrick Ohly
da80b554a7 DRA API: unify dropped field logic for ResourceClaim and ResourceClaimTemplate
The spec is the same in both, so those fields are now handled by common
code. For ResourceClaim spec updates, the "in use" check now only considers
the spec.

Theoretically some features could be in use in an old ResourceClaim status
and not in use in the spec. This can only occur in a spec update, which is
currently prevented because the entire spec is immutable. Even if it was
allowed, preventing adding disabled fields to the spec is the right thing to
do regardless of what may have ended up in the status earlier.
2025-10-21 12:22:52 +02:00