[PATCH] [TEST] Update SettingsDefineCapabilities.03 for LXC support
# HG changeset patch # User Guolian Yun <yunguol@cn.ibm.com> # Date 1213266000 -28800 # Node ID a69394e8052f65132dce5886e0a8670717133bf1 # Parent 254bc5464030a03b6f791fd49acd208f6ec1db23 [TEST] Update SettingsDefineCapabilities.03 for LXC support Signed-off-by: Guolian Yun <yunguol@cn.ibm.com> diff -r 254bc5464030 -r a69394e8052f suites/libvirt-cim/cimtest/SettingsDefineCapabilities/03_forward_errs.py --- a/suites/libvirt-cim/cimtest/SettingsDefineCapabilities/03_forward_errs.py Wed Jun 11 20:56:07 2008 +0800 +++ b/suites/libvirt-cim/cimtest/SettingsDefineCapabilities/03_forward_errs.py Thu Jun 12 18:20:00 2008 +0800 @@ -35,14 +35,16 @@ from CimTest.Globals import do_main, platform_sup from XenKvmLib.classes import get_typed_class +platform_sup = ['Xen', 'KVM', 'XenFV', 'LXC'] + expr_values = { "invalid_instid_keyname" : { 'rc' : pywbem.CIM_ERR_FAILED, - 'desc' : 'CIM_ERR_FAILED: Missing InstanceID'}, + 'desc' : 'Missing InstanceID'}, "invalid_instid_keyvalue" : { 'rc' : pywbem.CIM_ERR_FAILED, - 'desc' : 'CIM_ERR_FAILED: Unable to determine\ + 'desc' : 'Unable to determine\ resource type' }, "invalid_ccname_keyname" : { 'rc' : pywbem.CIM_ERR_INVALID_PARAMETER, - 'desc' : 'CIM_ERR_INVALID_PARAMETER' } + 'desc' : 'One or more parameter values passed to the method were invalid' } } def err_invalid_instid_keyname(virt, conn, field):
yunguol@cn.ibm.com wrote:
# HG changeset patch # User Guolian Yun <yunguol@cn.ibm.com> # Date 1213266000 -28800 # Node ID a69394e8052f65132dce5886e0a8670717133bf1 # Parent 254bc5464030a03b6f791fd49acd208f6ec1db23 [TEST] Update SettingsDefineCapabilities.03 for LXC support
Signed-off-by: Guolian Yun <yunguol@cn.ibm.com>
diff -r 254bc5464030 -r a69394e8052f suites/libvirt-cim/cimtest/SettingsDefineCapabilities/03_forward_errs.py
I saw the following failure: Testing LXC hypervisor SettingsDefineCapabilities - 03_forward_errs.py: FAIL ERROR - Unexpected rc code 4 and description CIM_ERR_INVALID_PARAMETER: WrongClassName.InstanceID="MemoryPool/0" ERROR - ------ FAILED: Invalid CCName Key Name.------ I also saw the same issue on Xen, XenFV, and KVM. -- Kaitlin Rupert IBM Linux Technology Center kaitlin@linux.vnet.ibm.com
libvirt-cim-bounces@redhat.com wrote on 2008-06-11 23:29:08:
yunguol@cn.ibm.com wrote:
# HG changeset patch # User Guolian Yun <yunguol@cn.ibm.com> # Date 1213266000 -28800 # Node ID a69394e8052f65132dce5886e0a8670717133bf1 # Parent 254bc5464030a03b6f791fd49acd208f6ec1db23 [TEST] Update SettingsDefineCapabilities.03 for LXC support
Signed-off-by: Guolian Yun <yunguol@cn.ibm.com>
diff -r 254bc5464030 -r a69394e8052f suites/libvirt- cim/cimtest/SettingsDefineCapabilities/03_forward_errs.py
I saw the following failure:
Testing LXC hypervisor SettingsDefineCapabilities - 03_forward_errs.py: FAIL ERROR - Unexpected rc code 4 and description CIM_ERR_INVALID_PARAMETER: WrongClassName.InstanceID="MemoryPool/0"
ERROR - ------ FAILED: Invalid CCName Key Name.------
I also saw the same issue on Xen, XenFV, and KVM.
Do you test it with Pegasus or SFCB? It passes with Pegasus when I test on your machine, and pass on Deepti's cimtest report. I think it fails with sfcb because that the WrongClassName can't be parsed by sfcb, so there is none output with the wrongclassname querying as follows: wbemcli ain -ac LXC_SettingsDefineCapabilities http://root:password@localhost/root/virt:WrongClassName.InstanceID="MemoryPool/0" However, we can get output with Pegasus. wbemcli ain -ac LXC_SettingsDefineCapabilities http://root:password@localhost/root/virt:WrongClassName.InstanceID="MemoryPool/0" * * wbemcli: Cim: (4) CIM_ERR_INVALID_PARAMETER: WrongClassName.InstanceID="MemoryPool/0" *
-- Kaitlin Rupert IBM Linux Technology Center kaitlin@linux.vnet.ibm.com
_______________________________________________ Libvirt-cim mailing list Libvirt-cim@redhat.com https://www.redhat.com/mailman/listinfo/libvirt-cim
I saw the following failure:
Testing LXC hypervisor SettingsDefineCapabilities - 03_forward_errs.py: FAIL ERROR - Unexpected rc code 4 and description CIM_ERR_INVALID_PARAMETER: WrongClassName.InstanceID="MemoryPool/0"
ERROR - ------ FAILED: Invalid CCName Key Name.------
I also saw the same issue on Xen, XenFV, and KVM.
Do you test it with Pegasus or SFCB?
I tested on Pegasus. However, it's passing for me now. Very strange. Can you resend the patch with just the LXC portion (since you sent a different patch to fix the description issue). Thanks! -- Kaitlin Rupert IBM Linux Technology Center kaitlin@linux.vnet.ibm.com
participants (3)
-
Guo Lian Yun -
Kaitlin Rupert -
yunguol＠cn.ibm.com