libvirt-cim-bounces@redhat.com wrote on 2009-03-25 01:03:33:
Guo Lian Yun wrote:
This tc fails for KVM with current src because of the exp_desc. The error desc expects to "The value supplied is incompatible with the
type" instead of "CIM_ERR_TYPE_MISMATCH" for KVM with current src.
But this tc with exp_desc of "CIM_ERR_TYPE_MISMATCH" pass for Xen with
current src. I'm not sure why it is? Why the error desc is different from Xen to KVM with the same libvit-cim version?
When I run on KVM, I see the following:
Testing KVM hypervisor -------------------------------------------------------------------- VirtualSystemManagementService - 17_removeresource_neg.py: FAIL InvokeMethod(RemoveResourceSettings): CIM_ERR_TYPE_MISMATCH 13 CIM_ERR_TYPE_MISMATCH --------------------------------------------------------------------
What error are you seeing? It outputs as follows: "The value supplied is incompatible with the type"
Just as you said, this bad inst will verify the COMOM instead of VSMS.RemoveRS() function. I create a DiskRASD with invalid InstanceID and pass to VSMS.RemoveRS() in #2 tc, and the tc works for me now. Thank for your help =)
-- 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