Thanks for the test run Deepti!
VSSD - 03_vssd_gi_errs.py: FAIL ERROR - Unexpected rc code 0 and description The web server returned a bad status line: '' ERROR - ------ FAILED: INVALID_InstID_Keyval ------
------------------------------------------------------------------------- cimserver o/p when run in the background misc_util.c(72): Connecting to libvirt with uri `qemu:///system' misc_util.c(199): URI of connection is: qemu:///system misc_util.c(72): Connecting to libvirt with uri `qemu:///system' misc_util.c(199): URI of connection is: qemu:///system Segmentation fault ------------------------------------------------------------------------- The segmentation fault occurs the InstanceID does not contain the VSType.
Can you give an example query? This test passes for me on my system, so I'm not sure what the offending portion of the test is. I tried the following query: wbemcli gi 'http://localhost:5988/root/virt:KVM_VirtualSystemSettingData.InstanceID="Invalid"' * * wbemcli: Cim: (6) CIM_ERR_NOT_FOUND: No such instance (InstanceID) * Which returned an error, as expected.
The segmentation does not occur when the InstanceID contains something like "KVM:Invaid"
VirtualSystemManagementService - 01_definesystem_name.py: FAIL VirtualSystemManagementService - 05_destroysystem_neg.py: FAIL VirtualSystemManagementService - 06_addresource.py: FAIL
VirtualSystemSettingDataComponent - 04_vssdc_rev_errs.py: FAIL ERROR - Unexpected rc code 0 and description The web server returned a bad status line: ''
ERROR - ------ FAILED: KVM_VirtualSystemSettingData INVALID_InstID_Keyval------
------------------------------------------------------------------------- cimserver o/p when run in the background misc_util.c(72): Connecting to libvirt with uri `qemu:///system' misc_util.c(199): URI of connection is: qemu:///system misc_util.c(72): Connecting to libvirt with uri `qemu:///system' misc_util.c(199): URI of connection is: qemu:///system std_association.c(288): Getting handler ... std_association.c(151): Calling Provider: 'associationVirt_VSSDComponent' std_association.c(167): Check client's assocClass: 'KVM_VirtualSystemSettingDataComponent' std_association.c(178): AssocClass valid. std_association.c(294): Getting handler succeeded. std_association.c(298): Calling handler ... std_association.c(301): Handler did not return CMPI_RC_OK. std_association.c(288): Getting handler ... std_association.c(151): Calling Provider: 'associationVirt_VSSDComponent' std_association.c(167): Check client's assocClass: 'KVM_VirtualSystemSettingDataComponent' std_association.c(178): AssocClass valid. std_association.c(294): Getting handler succeeded. std_association.c(298): Calling handler ... std_association.c(301): Handler did not return CMPI_RC_OK. Segmentation fault ------------------------------------------------------------------------- The segmentation fault occurs the InstanceID does not contain the VSType.
I had the same issue here - the test case passes. Can you give a sample query? Providers shouldn't seg fault, so it'll be good to track this down. Thanks!
The segmentation does not occur when the InstanceID contains something like "KVM:Invaid"
-- Kaitlin Rupert IBM Linux Technology Center kaitlin@linux.vnet.ibm.com