libvirt-cim-bounces@redhat.com wrote on 2008-04-24 02:34:02:
Zhengang Li wrote:
Distro: Fedora 9 Beta Kernel: 2.6.25-0.121.rc5.git4.fc9 Libvirt: 0.4.1-7.fc9 CIMOM: 2.7.0-6.fc9 PyWBEM: 0.6-1 libcmpiutil: 0.3-1.fc9 libvirt-cim: 0.3-4.fc9 cimtest: changeset-102
=========FAIL============= AllocationCapabilities - 02_alloccap_gi_errs.py: FAIL "Requested Object could not be found." vs. "Instance not found." error string issue. The return code is correct. [Known Issue]
ComputerSystemIndication - 01_created_indication.py: FAIL Exception : Authentication (or request) Failed! Previous tests were always on sfcb. Anyone has a successful experience on pegasus for indication?danms@us.ibm.com
I submitted a patch for this, which has been applied. Can someone update the indication_tester in the cimtest tree and test this out?
Cool! This test case passes with the updated indication_tester. The patch is only applied by libcmpiutil, so would you please update it synchronized under the cimtest tree? Thanks!
Thanks!
ElementAllocatedFromPool - 03_reverse_errs.py: FAIL exp: ERR_NOT_FOUND(6) - No such instance ret: ERR_FAILED(1) - Invalid InstanceID or unsupported pool type
ElementConforms - 02_reverse.py: FAIL Binary rpm provider returns CIM_ERR_INVALID_PARAMETER: KVM_ElementConformsToProfile on the following query: wbemain -ac KVM_ElementConformsToProfile 'http://u:p@host:5988/root/virt:KVM_ComputerSystem.
CreationClassName="KVM_ComputerSystem",Name="domgst"'
Same wbemcli command gets the correct results on another system using latest libvirt-cim tree (changeset 533).
Most of these issues appear to be due to a change in the providers, which is to be expected.
-- Kaitlin Rupert IBM Linux Technology Center kaitlin@linux.vnet.ibm.com
_______________________________________________ Libvirt-cim mailing list Libvirt-cim@redhat.com https://www.redhat.com/mailman/listinfo/libvirt-cim