CimTest Report for KVM on F9 30-04-2008
======================================================================== CIM Test Report for KVM on F9 with latest libvirt-cim and libcmpiutil ======================================================================== Distro : Fedora 9 Beta Kernel : 2.6.25-0.121.rc5.git4.fc9 Libvirt : libvirt-0.4.2-1.fc9.x86_64 CIMOM : pegasus PyWBEM : pywbem-0.6 CIM Schema : cimv216Experimental LibCMPIutil : 74 LibVirtCIM : 565 CIMTEST : 127 ======================================================= PASS : 90 FAIL : 18 XFAIL : 4 SKIP : 17 ----------------- Total : 129 ======================================================= List of tc that are failing ComputerSystem - 40_RSC_start.py: FAIL ComputerSystemIndication - 01_created_indication.py: FAIL ElementAllocatedFromPool - 04_forward_errs.py: FAIL ----Submitted fix for this ElementCapabilities - 01_forward.py: FAIL ElementSettingData - 01_forward.py: FAIL Memory - 02_defgetmem.py: FAIL NetworkPort - 03_user_netport.py: FAIL Processor - 02_definesys_get_procs.py: FAIL ResourcePoolConfigurationService - 03_CreateResourcePool.py: FAIL ResourcePoolConfigurationService - 04_CreateChildResourcePool.py: FAIL ResourcePoolConfigurationService - 06_RemoveResourcesFromResourcePool.py: FAIL ResourcePoolConfigurationService - 07_DeleteResourcePool.py: FAIL SettingsDefine - 02_reverse.py: FAIL 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. 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. The segmentation does not occur when the InstanceID contains something like "KVM:Invaid" Please find the complete report attached with the mail. Thanks and Regards, Deepti. Starting test suite: libvirt-cim Cleaned log files. Testing KVM hypervisor AllocationCapabilities - 01_enum.py: PASS AllocationCapabilities - 02_alloccap_gi_errs.py: PASS ComputerSystem - 01_enum.py: PASS ComputerSystem - 02_nosystems.py: PASS ComputerSystem - 03_defineVS.py: PASS ComputerSystem - 04_defineStartVS.py: PASS ComputerSystem - 05_activate_defined_start.py: XFAIL Bug: 85769 ERROR - ERROR: VS DomST1 transition from Defined State to Activate state was not Successful Bug:<85769> ComputerSystem - 06_paused_active_suspend.py: XFAIL Bug: 85769 ERROR - ERROR: VS DomST1 transition from suspend State to Activate state was not Successful Bug:<85769> ComputerSystem - 22_define_suspend.py: PASS ComputerSystem - 23_suspend_suspend.py: SKIP ComputerSystem - 27_define_suspend_errs.py: SKIP ComputerSystem - 32_start_reboot.py: SKIP ComputerSystem - 33_suspend_reboot.py: SKIP ComputerSystem - 35_start_reset.py: SKIP ComputerSystem - 40_RSC_start.py: FAIL ERROR - Unexpected rc code 1 and description: CIM_ERR_FAILED: ResourceSettings Error: Resource type not supported on this platform ERROR - Exception: ('Unable create domain %s using DefineSystem()', 'test_domain') InvokeMethod(DefineSystem): CIM_ERR_FAILED: ResourceSettings Error: Resource type not supported on this platform ComputerSystem - 41_cs_to_settingdefinestate.py: SKIP ComputerSystem - 42_cs_gi_errs.py: PASS ComputerSystemIndication - 01_created_indication.py: FAIL ERROR - error : (110, 'Connection timed out') ElementAllocatedFromPool - 01_forward.py: SKIP ElementAllocatedFromPool - 02_reverse.py: SKIP ElementAllocatedFromPool - 03_reverse_errs.py: PASS ElementAllocatedFromPool - 04_forward_errs.py: FAIL ERROR - Unexpected rc code 4 and description CIM_ERR_INVALID_PARAMETER: InvalidClassName.CreationClassName="KVM_LogicalDisk",DeviceID="hd_domain/hda",SystemCreationClassName="KVM_ComputerSystem",SystemName="hd_domain" ERROR - ------FAILED: Invalid classnameKeyname.------ ElementCapabilities - 01_forward.py: FAIL ERROR - ElementCapabilities association classname error ElementCapabilities - 02_reverse.py: PASS ElementCapabilities - 03_forward_errs.py: PASS ElementCapabilities - 04_reverse_errs.py: PASS ElementCapabilities - 05_hostsystem_cap.py: PASS ElementConforms - 01_forward.py: PASS ElementConforms - 02_reverse.py: PASS ElementConforms - 03_ectp_fwd_errs.py: PASS ElementConforms - 04_ectp_rev_errs.py: PASS ElementSettingData - 01_forward.py: FAIL ERROR - ElementSettingData returned 0 ProcResourceAllocationSettingData instances ERROR - Unable to get associated ResourceAllocationSettingData from ElementSettingData CIM_ERR_NOT_FOUND: No such instance (domu/proc) ElementSettingData - 03_esd_assoc_with_rasd_errs.py: PASS EnabledLogicalElementCapabilities - 01_enum.py: PASS EnabledLogicalElementCapabilities - 02_elecap_gi_errs.py: PASS HostSystem - 01_enum.py: PASS HostSystem - 02_hostsystem_to_rasd.py: PASS HostSystem - 03_hs_to_settdefcap.py: PASS HostSystem - 04_hs_to_EAPF.py: SKIP HostSystem - 05_hs_gi_errs.py: PASS HostSystem - 06_hs_to_vsms.py: PASS HostedDependency - 01_forward.py: PASS HostedDependency - 02_reverse.py: PASS HostedDependency - 03_enabledstate.py: PASS HostedDependency - 04_reverse_errs.py: PASS HostedResourcePool - 01_forward.py: PASS HostedResourcePool - 02_reverse.py: PASS HostedResourcePool - 03_forward_errs.py: PASS HostedResourcePool - 04_reverse_errs.py: PASS HostedService - 01_forward.py: PASS HostedService - 02_reverse.py: PASS HostedService - 03_forward_errs.py: PASS HostedService - 04_reverse_errs.py: PASS LogicalDisk - 01_disk.py: PASS LogicalDisk - 02_nodevs.py: PASS LogicalDisk - 03_ld_gi_errs.py: PASS Memory - 01_memory.py: PASS Memory - 02_defgetmem.py: FAIL ERROR - Unexpected rc code 1 and description: CIM_ERR_FAILED: ResourceSettings Error: Resource type not supported on this platform ERROR - Exception: Unable to create domain domu using DefineSys() InvokeMethod(DefineSystem): CIM_ERR_FAILED: ResourceSettings Error: Resource type not supported on this platform Memory - 03_mem_gi_errs.py: PASS NetworkPort - 01_netport.py: PASS NetworkPort - 02_np_gi_errors.py: PASS NetworkPort - 03_user_netport.py: FAIL ERROR - Exception: (6, u'CIM_ERR_NOT_FOUND: No such instance (test_domain/00:11:22:33:44:55)') Processor - 01_processor.py: PASS Processor - 02_definesys_get_procs.py: FAIL ERROR - Unexpected rc code 1 and description: CIM_ERR_FAILED: ResourceSettings Error: Resource type not supported on this platform ERROR - Exception: Unable create domain test_domain using DefineSystem() InvokeMethod(DefineSystem): CIM_ERR_FAILED: ResourceSettings Error: Resource type not supported on this platform Processor - 03_proc_gi_errs.py: PASS Profile - 01_enum.py: PASS Profile - 02_profile_to_elec.py: SKIP Profile - 03_rprofile_gi_errs.py: SKIP RASD - 01_verify_rasd_fields.py: PASS RASD - 02_enum.py: PASS RASD - 03_rasd_errs.py: PASS ReferencedProfile - 01_verify_refprof.py: PASS ReferencedProfile - 02_refprofile_errs.py: PASS ResourceAllocationFromPool - 01_forward.py: PASS ResourceAllocationFromPool - 02_reverse.py: PASS ResourceAllocationFromPool - 03_forward_errs.py: PASS ResourceAllocationFromPool - 04_reverse_errs.py: PASS ResourceAllocationFromPool - 05_RAPF_err.py: PASS ResourcePool - 01_enum.py: PASS ResourcePool - 02_rp_gi_errors.py: PASS ResourcePoolConfigurationCapabilities - 01_enum.py: PASS ResourcePoolConfigurationCapabilities - 02_rpcc_gi_errs.py: PASS ResourcePoolConfigurationService - 01_enum.py: PASS ResourcePoolConfigurationService - 02_rcps_gi_errors.py: PASS ResourcePoolConfigurationService - 03_CreateResourcePool.py: FAIL ERROR - Unexpected rc code 7 and description CIM_ERR_NOT_SUPPORTED InvokeMethod(CreateResourcePool): CIM_ERR_NOT_SUPPORTED ResourcePoolConfigurationService - 04_CreateChildResourcePool.py: FAIL ERROR - Unexpected rc code 7 and description CIM_ERR_NOT_SUPPORTED InvokeMethod(CreateChildResourcePool): CIM_ERR_NOT_SUPPORTED ResourcePoolConfigurationService - 05_AddResourcesToResourcePool.py: XFAIL Bug: 92173 ERROR - Unexpected rc code 1 and description CIM_ERR_FAILED: Unknown Method InvokeMethod(AddResourcesToResourcePool): CIM_ERR_FAILED: Unknown Method Bug:<92173> ResourcePoolConfigurationService - 06_RemoveResourcesFromResourcePool.py: FAIL ERROR - Unexpected rc code 7 and description CIM_ERR_NOT_SUPPORTED InvokeMethod(RemoveResourcesFromResourcePool): CIM_ERR_NOT_SUPPORTED ResourcePoolConfigurationService - 07_DeleteResourcePool.py: FAIL ERROR - Unexpected rc code 7 and description CIM_ERR_NOT_SUPPORTED InvokeMethod(DeleteResourcePool): CIM_ERR_NOT_SUPPORTED SettingsDefine - 01_forward.py: PASS SettingsDefine - 02_reverse.py: FAIL ERROR - Mistmatching value for VSSDComponent association CIM_ERR_NOT_FOUND: No such instance (virtgst/proc) SettingsDefine - 03_sds_fwd_errs.py: PASS SettingsDefine - 04_sds_rev_errs.py: PASS SettingsDefineCapabilities - 01_forward.py: SKIP SettingsDefineCapabilities - 03_forward_errs.py: PASS SettingsDefineCapabilities - 04_forward_vsmsdata.py: PASS SettingsDefineCapabilities - 05_reverse_vsmcap.py: PASS SystemDevice - 01_forward.py: PASS SystemDevice - 02_reverse.py: PASS SystemDevice - 03_fwderrs.py: PASS VSSD - 01_enum.py: PASS VSSD - 02_bootldr.py: SKIP VSSD - 04_vssd_to_rasd.py: PASS 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 ------ VirtualSystemManagementCapabilities - 01_enum.py: PASS VirtualSystemManagementCapabilities - 02_vsmcap_gi_errs.py: PASS VirtualSystemManagementService - 01_definesystem_name.py: FAIL ERROR - Unexpected rc code 1 and description: CIM_ERR_FAILED: ResourceSettings Error: Resource type not supported on this platform InvokeMethod(DefineSystem): CIM_ERR_FAILED: ResourceSettings Error: Resource type not supported on this platform VirtualSystemManagementService - 02_destroysystem.py: PASS VirtualSystemManagementService - 03_definesystem_ess.py: PASS VirtualSystemManagementService - 04_definesystem_ers.py: PASS VirtualSystemManagementService - 05_destroysystem_neg.py: FAIL ERROR - destroy_fail>>noname: Error executing DestroySystem, exception details below ERROR - (1, u'CIM_ERR_FAILED: Unable to retrieve domain name.') ERROR - destroy_fail>>nonexistent: Error executing DestroySystem, exception details below ERROR - (1, u'CIM_ERR_FAILED: Failed to find domain') InvokeMethod(DestroySystem): CIM_ERR_FAILED: Unable to retrieve domain name. InvokeMethod(DestroySystem): CIM_ERR_FAILED: Failed to find domain VirtualSystemManagementService - 06_addresource.py: FAIL ERROR - Error invoking AddRS ERROR - (1, u'CIM_ERR_FAILED: Failed to create domain') InvokeMethod(AddResourceSettings): CIM_ERR_FAILED: Failed to create domain VirtualSystemManagementService - 07_addresource_neg.py: PASS VirtualSystemManagementService - 08_modifyresource.py: XFAIL Bug: 90853 ERROR - Error invoking ModifyRS ERROR - (1, u'CIM_ERR_FAILED: Failed to create domain') InvokeMethod(ModifyResourceSettings): CIM_ERR_FAILED: Failed to create domain Bug:<90853> VirtualSystemMigrationCapabilities - 01_enum.py: PASS VirtualSystemMigrationCapabilities - 02_vsmc_gi_errs.py: PASS VirtualSystemMigrationService - 01_migratable_host.py: SKIP VirtualSystemMigrationService - 02_host_migrate_type.py: SKIP VirtualSystemMigrationService - 05_migratable_host_errs.py: SKIP VirtualSystemMigrationSettingData - 01_enum.py: PASS VirtualSystemMigrationSettingData - 02_vsmsd_gi_errs.py: PASS VirtualSystemSettingDataComponent - 01_forward.py: SKIP VirtualSystemSettingDataComponent - 02_reverse.py: PASS VirtualSystemSettingDataComponent - 03_vssdc_fwd_errs.py: PASS 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------ VirtualSystemSnapshotService - 01_enum.py: PASS VirtualSystemSnapshotService - 02_vs_sservice_gi_errs.py: PASS VirtualSystemSnapshotServiceCapabilities - 01_enum.py: PASS VirtualSystemSnapshotServiceCapabilities - 02_vs_sservicecap_gi_errs.py: PASS
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
Please see my replies inline. Thanks and Regards, Deepti. Kaitlin Rupert wrote:
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 same query on my machine gives a segmentation fault.
wbemcli gi http://localhost:5988/root/virt:KVM_VirtualSystemSettingData.InstanceID="invalid" * * wbemcli: Http Exception: Server returned nothing (no headers, no data) * I have Revision="565" of libvirt-cim installed on my machine.
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"
wbemcli ain -ac KVM_VirtualSystemSettingDataComponent 'http://localhost:5988/root/virt:KVM_VirtualSystemSettingData.InstanceID="wrong"' * * wbemcli: Http Exception: Server returned nothing (no headers, no data) * Its strange why this is happening only on my machine. This is on latest libvirt-cim on F9 . I get the expected error message when I pass the VSType as part of the InstanceID. wbemcli gi http://root:vsm4you@localhost:5988/root/virt:KVM_VirtualSystemSettingData.InstanceID="KVM:invalid"* * wbemcli: Cim: (6) CIM_ERR_NOT_FOUND: No such instance (invalid) *
participants (2)
-
Deepti B Kalakeri -
Kaitlin Rupert