
9 Jan
2008
9 Jan
'08
12:09 p.m.
The starting point for this patch series was the missing validation of the client's given object path of ResourceAllocationSettingData in the RAFP provider. This is fixed by patch #1. Patch #2 switches the return code for getInstance from FAILED to NOT_FOUND for ResourceAllocationSettingData. Patch #3 registeres the RASD provider for KVM. Patch #4 switches the return code for getInstance from FAILED to NOT_FOUND for DevicePools.