4:07 a.m.
========================================================================
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 : 83
LibVirtCIM : 660
CIMTEST : 282
=======================================================
PASS : 120
FAIL : 4
XFAIL : 2
SKIP : 7
-----------------
Total : 133
=======================================================
Here is one of the tc that failed:
ComputerSystemIndication - 01_created_indication.py: FAIL
Need to verify this.
ResourceAllocationFromPool - 01_forward.py: FAIL
ResourceAllocationFromPool - 02_reverse.py: FAIL
Fix for this is submitted by Daisy.
This tc passed when run manually.
HostSystem - 04_hs_to_EAPF.py: FAIL
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: PASS
ComputerSystem - 06_paused_active_suspend.py: PASS
ComputerSystem - 22_define_suspend.py: PASS
ComputerSystem - 23_suspend_suspend.py: PASS
ComputerSystem - 27_define_suspend_errs.py: SKIP
libvir: error : this function is not supported by the hypervisor: virDomainReboot
ComputerSystem - 32_start_reboot.py: XFAIL Bug: 00002
ERROR - Exception: (1, u'CIM_ERR_FAILED: Domain Operation Failed')
ERROR - Unable to 'Reboot' dom 'cs_test_domain' using
RequestedStateChange()
InvokeMethod(RequestStateChange): CIM_ERR_FAILED: Domain Operation Failed
Bug:<00002>
ComputerSystem - 33_suspend_reboot.py: XFAIL Bug: 00002
ERROR - Exception: (1, u'CIM_ERR_FAILED: Domain not running')
ERROR - Unable to 'Reboot' dom 'test_domain' using
RequestedStateChange()
InvokeMethod(RequestStateChange): CIM_ERR_FAILED: Domain not running
Bug:<00002>
ComputerSystem - 35_start_reset.py: PASS
ComputerSystem - 40_RSC_start.py: PASS
ComputerSystem - 41_cs_to_settingdefinestate.py: SKIP
ComputerSystem - 42_cs_gi_errs.py: PASS
ComputerSystemIndication - 01_created_indication.py: FAIL
ERROR - Waited too long for indication
ElementAllocatedFromPool - 01_forward.py: PASS
ElementAllocatedFromPool - 02_reverse.py: PASS
ElementAllocatedFromPool - 03_reverse_errs.py: PASS
ElementAllocatedFromPool - 04_forward_errs.py: PASS
ElementCapabilities - 01_forward.py: PASS
ElementCapabilities - 02_reverse.py: PASS
libvir: QEMU error : Domain not found
libvir: Domain error : invalid domain pointer in virDomainFree
ElementCapabilities - 03_forward_errs.py: PASS
libvir: QEMU error : Domain not found
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
libvir: QEMU error : Domain not found
libvir: Domain error : invalid domain pointer in virDomainFree
ElementConforms - 04_ectp_rev_errs.py: PASS
ElementSettingData - 01_forward.py: PASS
ElementSettingData - 03_esd_assoc_with_rasd_errs.py: PASS
EnabledLogicalElementCapabilities - 01_enum.py: PASS
libvir: QEMU error : Domain not found
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: FAIL
ERROR - KVM_ElementAllocatedFromPool returned 0 Logical Devices objects
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: PASS
Memory - 03_mem_gi_errs.py: PASS
NetworkPort - 01_netport.py: PASS
NetworkPort - 02_np_gi_errors.py: PASS
NetworkPort - 03_user_netport.py: PASS
Processor - 01_processor.py: PASS
Processor - 02_definesys_get_procs.py: PASS
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: PASS
RASD - 01_verify_rasd_fields.py: PASS
RASD - 02_enum.py: PASS
RASD - 03_rasd_errs.py: PASS
RASD - 04_disk_rasd_size.py: PASS
ReferencedProfile - 01_verify_refprof.py: PASS
ReferencedProfile - 02_refprofile_errs.py: PASS
ResourceAllocationFromPool - 01_forward.py: FAIL
ERROR - Return NULL, expect at least one instance
ResourceAllocationFromPool - 02_reverse.py: FAIL
ERROR - InstanceID Mismatch
ERROR - Returned NetworkPool/default-net14 instead of NetworkPool/default-net94
ResourceAllocationFromPool - 03_forward_errs.py: PASS
ResourceAllocationFromPool - 04_reverse_errs.py: PASS
libvir: Network error : invalid network pointer in virNetworkFree
libvir: QEMU error : Network not found: no network with matching name
libvir: Network error : invalid network pointer in virNetworkFree
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: PASS
ResourcePoolConfigurationService - 04_CreateChildResourcePool.py: PASS
ResourcePoolConfigurationService - 05_AddResourcesToResourcePool.py: PASS
ResourcePoolConfigurationService - 06_RemoveResourcesFromResourcePool.py: PASS
ResourcePoolConfigurationService - 07_DeleteResourcePool.py: PASS
SettingsDefine - 01_forward.py: PASS
SettingsDefine - 02_reverse.py: PASS
SettingsDefine - 03_sds_fwd_errs.py: PASS
SettingsDefine - 04_sds_rev_errs.py: PASS
SettingsDefineCapabilities - 01_forward.py: PASS
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 - 03_vssd_gi_errs.py: PASS
VSSD - 04_vssd_to_rasd.py: PASS
VirtualSystemManagementCapabilities - 01_enum.py: PASS
VirtualSystemManagementCapabilities - 02_vsmcap_gi_errs.py: PASS
VirtualSystemManagementService - 01_definesystem_name.py: PASS
VirtualSystemManagementService - 02_destroysystem.py: PASS
error line 1: syntax error in 'wrong'
VirtualSystemManagementService - 03_definesystem_ess.py: PASS
error line 1: syntax error in 'wrong'
VirtualSystemManagementService - 04_definesystem_ers.py: PASS
libvir: Domain error : invalid domain pointer in virDomainFree
libvir: QEMU error : Domain not found
libvir: Domain error : invalid domain pointer in virDomainFree
VirtualSystemManagementService - 05_destroysystem_neg.py: PASS
VirtualSystemManagementService - 06_addresource.py: PASS
error line 1: syntax error in 'ever'
VirtualSystemManagementService - 07_addresource_neg.py: PASS
VirtualSystemManagementService - 08_modifyresource.py: PASS
VirtualSystemManagementService - 09_procrasd_persist.py: PASS
VirtualSystemManagementService - 10_hv_version.py: PASS
VirtualSystemManagementService - 11_define_memrasdunits.py: PASS
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: PASS
VirtualSystemSettingDataComponent - 02_reverse.py: PASS
VirtualSystemSettingDataComponent - 03_vssdc_fwd_errs.py: PASS
VirtualSystemSettingDataComponent - 04_vssdc_rev_errs.py: PASS
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
10:36 a.m.
Deepti B Kalakeri wrote:
========================================================================
CIM Test Report for KVM on F9 with latest libvirt-cim and libcmpiutil
========================================================================
This tc passed when run manually.
HostSystem - 04_hs_to_EAPF.py: FAIL
Any thoughts as to why this fails in the bulk run? Sounds like one of
the tests alters the environment in a way that this test isn't expecting.
-
Kaitlin Rupert
IBM Linux Technology Center
kaitlin(a)linux.vnet.ibm.com
7:53 a.m.
List for discussion and development of libvirt CIM <libvirt-cim(a)redhat.com>
Kaitlin Rupert wrote:
Deepti B Kalakeri wrote:
> ========================================================================
> CIM Test Report for KVM on F9 with latest libvirt-cim and libcmpiutil
> ========================================================================
>
> This tc passed when run manually.
> HostSystem - 04_hs_to_EAPF.py: FAIL
>
Any thoughts as to why this fails in the bulk run? Sounds like one of
the tests alters the environment in a way that this test isn't expecting.
I did
not find anything common in the other test case which could be
making the HostSystem - 04_hs_to_EAPF.py tc to fail.
I tried reproducing the problem for KVM by running all the HostSystem
tc, but this time the tc did not fail for me in the batch run.
The above test case has passed for XenFV test runs till now.
I tried batch run of the HostSystem directory for XenFV and the tc
failed bcs of the following reason:
HostSystem - 04_hs_to_EAPF.py: FAIL
ERROR - DeviceID Mismatch
ERROR - Returned CrossClass_GuestDom/hda instead of
CrossClass_GuestDom/xvdb
I went through the test case and found to have the following problems
with the test case:
1) The XML configuration information with the existing test case is
not completely correct for *creating* a KVM/XenFV guest.
It does not set the test_disk information correctly, but this
does not matter when we just *define *the guest, but surely the XML
config was not useful in *creating* the KVM/XenFV guest.
The test_disk was set to 'xvdb' for all Xen/XenFV/KVM.
2) The network pool information that is used for creating the guest
and the networkpool used in the rest of the test case are different.
3) The tc was using create_diskpool_file() function to create a
DiskPool, this should have been create_diskpool_conf() which calls
either creating of diskconf file or using the diskpool
depending on the version of the libvirt on the machine.
4) Also, the networkpool information that was initialized using the
pool_init_list() test case was getting overwritten in the case where
there were more than one networkpool existed.
And this could be one of the potential reason for the test case
to be intermittently fail, since the information in the list would not
have been set appropriately.
The patch with the fixes is on way.
If anyone else has any other idea of debugging this problem ?
Thanks and Regards,
Deepti.
-
Kaitlin Rupert
IBM Linux Technology Center
kaitlin(a)linux.vnet.ibm.com
_______________________________________________
Libvirt-cim mailing list
Libvirt-cim(a)redhat.com
https://www.redhat.com/mailman/listinfo/libvirt-cim
3:39 p.m.
I went through the test case and found to have the following
problems
with the test case:
1) The XML configuration information with the existing test case is
not completely correct for *creating* a KVM/XenFV guest.
It does not set the test_disk information correctly, but this does
not matter when we just *define *the guest, but surely the XML config
was not useful in *creating* the KVM/XenFV guest.
The test_disk was set to 'xvdb' for all Xen/XenFV/KVM.
2) The network pool information that is used for creating the guest
and the networkpool used in the rest of the test case are different.
3) The tc was using create_diskpool_file() function to create a
DiskPool, this should have been create_diskpool_conf() which calls
either creating of diskconf file or using the diskpool
depending on the version of the libvirt on the machine.
4) Also, the networkpool information that was initialized using the
pool_init_list() test case was getting overwritten in the case where
there were more than one networkpool existed.
And this could be one of the potential reason for the test case to
be intermittently fail, since the information in the list would not have
been set appropriately.
Yep, I agree here. I was seeing this fail when I had more than one
network pool defined because the guest was using one pool but the test
was comparing against a different pool.
Thanks for looking at this test - looks like a lot of issues to fix.
--
Kaitlin Rupert
IBM Linux Technology Center
kaitlin(a)linux.vnet.ibm.com
5977
days inactive
5982
days old
3 comments
2 participants
participants (2)
-
Deepti B Kalakeri -
Kaitlin Rupert