[Libvirt-cim] Re: Test Run Summary (Aug 27 2009): KVM on Fedora release 11 (Leonidas) with Pegasuslist

Deepti B Kalakeri wrote: > ================================================= > Test Run Summary (Aug 27 2009): KVM on Fedora release 11 (Leonidas) > with Pegasus > ================================================= > Distro: Fedora release 11 (Leonidas) > Kernel: 2.6.27.5-117.fc10.x86_64 > libvirt: 0.7.0 > Hypervisor: QEMU 0.10.1 > CIMOM: Pegasus 2.9.0 > Libvirt-cim revision: 963 > Libvirt-cim changeset: 5a1871168fd4 > Cimtest revision: 766 > Cimtest changeset: 3c09a49a30f4 > ================================================= > FAIL : 6 > XFAIL : 4 > SKIP : 11 > PASS : 146 > ----------------- > Total : 167 > ================================================= > FAIL Test Summary: > ComputerSystemIndication - 01_created_indication.py: FAIL > ElementAllocatedFromPool - 01_forward.py: FAIL This is not a test case issue. The test failed because there were two conflicting diskpool with the same target dir used while creating it. # virsh pool-list --all Name State Autostart ----------------------------------------- cimtest-diskpool active no tmp active no virsh pool-dumpxml cimtest-diskpool <pool type='dir'> <name>cimtest-diskpool</name> <uuid>e45c9d25-b143-52bd-ccf5-e2f8cd8e8acd</uuid> <capacity>42275766272</capacity> <allocation>8330838016</allocation> <available>33944928256</available> <source> </source> <target> <path>/tmp</path> <permissions> <mode>0700</mode> <owner>0</owner> <group>0</group> </permissions> </target> </pool> # virsh pool-dumpxml tmp <pool type='dir'> <name>tmp</name> <uuid>40c687d1-dccb-226b-0234-8fdb18c5e1c9</uuid> <capacity>42275766272</capacity> <allocation>7913541632</allocation> <available>34362224640</available> <source> </source> <target> <path>/tmp</path> <permissions> <mode>0700</mode> <owner>0</owner> <group>0</group> </permissions> </target> </pool> The following query was failing to return cimtest-diskpool and instead returned DiskPool/tmp because of which the test failed: #wbemcli ain -ac KVM_ElementAllocatedFromPool http://root:<passwd>@localhost:5988/root/virt:KVM_LogicalDisk.Creat... <hostname>/root/virt:KVM_DiskPool.InstanceID="DiskPool/tmp" Once I deleted the tmp diskpool and reran the test it passed. #wbemcli ain -ac KVM_ElementAllocatedFromPool http://root:<passwd>@localhost:5988/root/virt:KVM_LogicalDisk.Creat... <hostname>/root/virt:KVM_DiskPool.InstanceID="DiskPool/cimtest-diskpool" So, I think libvirt should have not allowed to create two pools which used the same target path, or libvirt-cim will have to handle this condition. > HostSystem - 03_hs_to_settdefcap.py: FAIL > ResourceAllocationFromPool - 01_forward.py: FAIL > ResourceAllocationFromPool - 02_reverse.py: FAIL

> VirtualSystemManagementService - 15_mod_system_settings.py: FAIL > will look into the above