Re: [Libvirt-cim] [PATCH] [TEST] Updating RPCS/10_create_storagevolume.py
Deepti B. Kalakeri wrote:
# HG changeset patch
# User Deepti B. Kalakeri <deeptik(a)linux.vnet.ibm.com>
# Date 1253097826 14400
# Node ID 0a64f90aabb5dd63ac2ab677981a939b2fcf5eeb
# Parent 9e08670a3c3749738a65fec7f2faa4c2b68a7092
[TEST] Updating RPCS/10_create_storagevolume.py
Updating RPCS/10_create_storagevolume.py to create and use its own dir pool for
StorageVol.
If we try to use the default_pool_name then this will cause regression in the further
tests which
refer to the /tmp/cimtest-vol.img as all the information regarding this will get cleared
only
when the pool under which it is created it destoyed.
Not sure what I understand what you mean here. Why not make sure
/tmp/cimtest-vol.img is removed before the test exits? Then you can
create the image in the default pool. Just remove the volume when
you're done.
I think you can still use the default pool if you'd like, but either
approach is fine. However, it looks like you create a new diskpool, but
the storage volume is still being created in /tmp.
When I print the disk RASD:
root/virt:KVM_DiskPool.InstanceID="DiskPool/DISK_POOL_DIR"
When I print the exp_vol_path: /tmp/cimtest-vol.img
The test still passed because vol_list() returns the list of volumes in
/tmp, even though the pool_name is DISK_POOL_DIR - so something is off
here. Can you take a look to see what might be causing this?
--
Kaitlin Rupert
IBM Linux Technology Center
kaitlin(a)linux.vnet.ibm.com