Re: Fw: [TEST] Test failure summary for Xen/XenFV with and without sblim base providers with current resource
Guo Lian Yun/China/IBM wrote on 2008-09-10 15:46:25:
Deepti,
Here is my updates today.
Xen (8)
XenFV (11)
Xen with sblim base providers installed (33)
Person Responsible
ComputerSystem - 01_enum.py
ComputerSystem - 32_start_reboot.py
ComputerSystem - 32_start_reboot.py
ComputerSystem - 32_start_reboot.py
submitted patch for this.
ElementCapabilities - 01_forward.py
ElementCapabilities - 02_reverse.py
ElementCapabilities - 05_hostsystem_cap.py
ElementConforms - 01_forward.py
ElementConforms - 02_reverse.py
EnabledLogicalElementCapabilities - 01_enum.py
The Host* related tests fails because that I get none when enumerate HostSystem with sblim base provider installed. Below query return NULL to me. wbemcli ein http://root:password@localhost/root/virt:Xen_HostSystem Here is the output when I debug HostSystem - 01_enum.py test case. Virt_HostSystem.c(164): SBLIM: Returned instance misc_util.c(72): Connecting to libvirt with uri `xen' misc_util.c(199): URI of connection is: xen:/// Virt_HostSystem.c(164): SBLIM: Returned instance I will continue to look into this, please let me know if you know more about it. Thanks!
HostSystem - 01_enum.py
HostSystem - 02_hostsystem_to_rasd.py
HostSystem - 03_hs_to_settdefcap.py
HostSystem - 04_hs_to_EAPF.py
HostSystem - 05_hs_gi_errs.py
HostSystem - 06_hs_to_vsms.py
HostedDependency - 01_forward.py
HostedDependency - 02_reverse.py
HostedDependency - 03_enabledstate.py
HostedDependency - 04_reverse_errs.py
HostedResourcePool - 01_forward.py
HostedResourcePool - 02_reverse.py
HostedResourcePool - 03_forward_errs.py
HostedService - 01_forward.py
HostedService - 02_reverse.py
HostedService - 03_forward_errs.py
HostedService - 04_reverse_errs.py
LogicalDisk - 02_nodevs.py
#2 patch under review
LogicalDisk - 03_ld_gi_errs.py
LogicalDisk - 03_ld_gi_errs.py
fix
Memry - 01_memory.py
Memory - 01_memory.py
fix
NetworkPort - 01_netport.py
NetworkPort - 01_netport.py
fix
RASD - 02_enum.py
fix
ResourceAllocationFromPool - 01_forward.py
fix
ResourceAllocationFromPool - 05_RAPF_err.py
fix
ResourcePoolConfigurationService - 01_enum.py
ResourcePoolConfigurationService - 02_rcps_gi_errors.py
VSSD - 02_bootldr.py
VSSD - 02_bootldr.py
#2 patch under review
VSSD - 04_vssd_to_rasd.py
VSSD - 04_vssd_to_rasd.py
#2 patch under review
VirtualSystemManagementService - 06_addresource.py
VirtualSystemManagementService - 06_addresource.py
VirtualSystemManagementService - 06_addresource.py
Sent the tc failures analysis
VirtualSystemManagementService - 08_modifyresource.py
VirtualSystemManagementService - 08_modifyresource.py
VirtualSystemManagementService - 08_modifyresource.py
This did not fail again for me.
VirtualSystemMigrationService - 02_host_migrate_type.py
Under analysis.
VirtualSystemSnapshotService - 01_enum.py
VirtualSystemSnapshotService - 02_vs_sservice_gi_errs.py
Best, Regards
Daisy (运国莲) VSM Team, China Systems & Technology Labs (CSTL) E-mail: yunguol@cn.ibm.com TEL: (86)-21-60922403 Building 10, 399 Ke Yuan Rd, Pudong Shanghai, 201203
----- Forwarded by Guo Lian Yun/China/IBM on 2008-09-10 15:46 -----
Guo Lian Yun/China/IBM 2008-09-09 14:36
To
Deepti B Kalakeri/India/IBM@IBMIN@IBMAU
cc
Kaitlin Rupert/Beaverton/IBM@IBMUS
Subject
Re: [TEST] Test failure summary for Xen/XenFV with and without sblim base providers with current resource
Update the table.
Xen (8)
XenFV (11)
Xen with sblim base providers installed (33)
Person Responsible
ComputerSystem - 01_enum.py
ComputerSystem - 32_start_reboot.py
ComputerSystem - 32_start_reboot.py
ComputerSystem - 32_start_reboot.py
submitted patch for this.
ElementCapabilities - 01_forward.py
ElementCapabilities - 02_reverse.py
ElementCapabilities - 05_hostsystem_cap.py
ElementConforms - 01_forward.py
ElementConforms - 02_reverse.py
EnabledLogicalElementCapabilities - 01_enum.py
HostSystem - 01_enum.py
HostSystem - 02_hostsystem_to_rasd.py
HostSystem - 03_hs_to_settdefcap.py
HostSystem - 04_hs_to_EAPF.py
HostSystem - 05_hs_gi_errs.py
HostSystem - 06_hs_to_vsms.py
HostedDependency - 01_forward.py
HostedDependency - 02_reverse.py
HostedDependency - 03_enabledstate.py
HostedDependency - 04_reverse_errs.py
HostedResourcePool - 01_forward.py
HostedResourcePool - 02_reverse.py
HostedResourcePool - 03_forward_errs.py
HostedService - 01_forward.py
HostedService - 02_reverse.py
HostedService - 03_forward_errs.py
HostedService - 04_reverse_errs.py
LogicalDisk - 02_nodevs.py
Patch under review
LogicalDisk - 03_ld_gi_errs.py
LogicalDisk - 03_ld_gi_errs.py
Patch under review
Memry - 01_memory.py
Memory - 01_memory.py
Patch under review
NetworkPort - 01_netport.py
NetworkPort - 01_netport.py
Patch under review
RASD - 02_enum.py
Patch under review
ResourceAllocationFromPool - 01_forward.py
Patch under review
ResourceAllocationFromPool - 05_RAPF_err.py
Patch under review
ResourcePoolConfigurationService - 01_enum.py
ResourcePoolConfigurationService - 02_rcps_gi_errors.py
VSSD - 02_bootldr.py
VSSD - 02_bootldr.py
VSSD - 04_vssd_to_rasd.py
VSSD - 04_vssd_to_rasd.py
VirtualSystemManagementService - 06_addresource.py
VirtualSystemManagementService - 06_addresource.py
VirtualSystemManagementService - 06_addresource.py
Sent the tc failures analysis
VirtualSystemManagementService - 08_modifyresource.py
VirtualSystemManagementService - 08_modifyresource.py
VirtualSystemManagementService - 08_modifyresource.py
This did not fail again for me.
VirtualSystemMigrationService - 02_host_migrate_type.py
Under analysis.
VirtualSystemSnapshotService - 01_enum.py
VirtualSystemSnapshotService - 02_vs_sservice_gi_errs.py
Best, Regards
Daisy (运国莲) VSM Team, China Systems & Technology Labs (CSTL) E-mail: yunguol@cn.ibm.com TEL: (86)-21-60922403 Building 10, 399 Ke Yuan Rd, Pudong Shanghai, 201203
Deepti B Kalakeri/India/IBM@IBMIN 2008-09-05 20:59
To
Guo Lian Yun/China/IBM@IBMCN@IBMAU
cc
Kaitlin Rupert/Beaverton/IBM@IBMUS, Kaitlin Rupert/Beaverton/IBM@IBMUS
Subject
Re: [TEST] Test failure summary for Xen/XenFV with and without sblim base providers with current resource
Updated the table.
Xen (8)
XenFV (11)
Xen with sblim base providers installed (33)
Person Responsible
ComputerSystem - 01_enum.py
ComputerSystem - 32_start_reboot.py
ComputerSystem - 32_start_reboot.py
ComputerSystem - 32_start_reboot.py
submitted patch for this.
ElementCapabilities - 01_forward.py
ElementCapabilities - 02_reverse.py
ElementCapabilities - 05_hostsystem_cap.py
ElementConforms - 01_forward.py
ElementConforms - 02_reverse.py
EnabledLogicalElementCapabilities - 01_enum.py
HostSystem - 01_enum.py
HostSystem - 02_hostsystem_to_rasd.py
HostSystem - 03_hs_to_settdefcap.py
HostSystem - 04_hs_to_EAPF.py
HostSystem - 05_hs_gi_errs.py
HostSystem - 06_hs_to_vsms.py
HostedDependency - 01_forward.py
HostedDependency - 02_reverse.py
HostedDependency - 03_enabledstate.py
HostedDependency - 04_reverse_errs.py
HostedResourcePool - 01_forward.py
HostedResourcePool - 02_reverse.py
HostedResourcePool - 03_forward_errs.py
HostedService - 01_forward.py
HostedService - 02_reverse.py
HostedService - 03_forward_errs.py
HostedService - 04_reverse_errs.py
LogicalDisk - 02_nodevs.py
LogicalDisk - 03_ld_gi_errs.py
LogicalDisk - 03_ld_gi_errs.py
Memry - 01_memory.py
Memory - 01_memory.py
NetworkPort - 01_netport.py
NetworkPort - 01_netport.py
RASD - 02_enum.py
ResourceAllocationFromPool - 01_forward.py
ResourceAllocationFromPool - 05_RAPF_err.py
ResourcePoolConfigurationService - 01_enum.py
ResourcePoolConfigurationService - 02_rcps_gi_errors.py
VSSD - 02_bootldr.py
VSSD - 02_bootldr.py
VSSD - 04_vssd_to_rasd.py
VSSD - 04_vssd_to_rasd.py
VirtualSystemManagementService - 06_addresource.py
VirtualSystemManagementService - 06_addresource.py
VirtualSystemManagementService - 06_addresource.py
Sent the tc failures analysis
VirtualSystemManagementService - 08_modifyresource.py
VirtualSystemManagementService - 08_modifyresource.py
VirtualSystemManagementService - 08_modifyresource.py
This did not fail again for me.
VirtualSystemMigrationService - 02_host_migrate_type.py
Under analysis.
VirtualSystemSnapshotService - 01_enum.py
VirtualSystemSnapshotService - 02_vs_sservice_gi_errs.py
Thanks and Regards, Deepti.
The Host* related tests fails because that I get none when enumerate HostSystem with sblim base provider installed. Below query return NULL to me. wbemcli ein http://root:password@localhost/root/virt:Xen_HostSystem
Here is the output when I debug HostSystem - 01_enum.py test case. Virt_HostSystem.c(164): SBLIM: Returned instance misc_util.c(72): Connecting to libvirt with uri `xen' misc_util.c(199): URI of connection is: xen:/// Virt_HostSystem.c(164): SBLIM: Returned instance
I will continue to look into this, please let me know if you know more about it.
Thanks!
This is the intended behavior. The HosySystem class is just a placeholder - if the guest has the SBLIM providers installed, then the proper class to represent the host is Linux_ComputerSystem (this is the SBLIM provider that represents the "base" or host system). We don't want the HostSystem provider to return anything in this case, because there's no need for a placeholder. -- Kaitlin Rupert IBM Linux Technology Center kaitlin@linux.vnet.ibm.com
libvirt-cim-bounces@redhat.com wrote on 2008-09-12 04:00:48:
The Host* related tests fails because that I get none when enumerate HostSystem with sblim base provider installed. Below query return NULL to me. wbemcli ein http://root:password@localhost/root/virt:Xen_HostSystem
Here is the output when I debug HostSystem - 01_enum.py test case. Virt_HostSystem.c(164): SBLIM: Returned instance misc_util.c(72): Connecting to libvirt with uri `xen' misc_util.c(199): URI of connection is: xen:/// Virt_HostSystem.c(164): SBLIM: Returned instance
I will continue to look into this, please let me know if you know more
about it.
Thanks!
This is the intended behavior. The HosySystem class is just a placeholder - if the guest has the SBLIM providers installed, then the proper class to represent the host is Linux_ComputerSystem (this is the SBLIM provider that represents the "base" or host system).
We don't want the HostSystem provider to return anything in this case, because there's no need for a placeholder.
If the HostSystem provider return NULL, how to make test case work? Because the test expects to return at least one Xen_HostSystem instance. Would you please explain more for me on this? Any suggestion on fixing them? Thanks!
-- 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
This is the intended behavior. The HosySystem class is just a placeholder - if the guest has the SBLIM providers installed, then the proper class to represent the host is Linux_ComputerSystem (this is the SBLIM provider that represents the "base" or host system).
We don't want the HostSystem provider to return anything in this case, because there's no need for a placeholder.
If the HostSystem provider return NULL, how to make test case work? Because the test expects to return at least one Xen_HostSystem instance. Would you please explain more for me on this? Any suggestion on fixing them?
The test behavior needs to be changed for the sblim case. 1) If SBLIM: Enum of HostSystem doesn't return any instances 2) If not SBLIM: Enum of HostSystem returns a single instance If you take a look at the get_host() in Virt_HostSystem.c, you'll get an understanding of how the providers determine whether a SBLIM instance is available on the system. Does this help? -- Kaitlin Rupert IBM Linux Technology Center kaitlin@linux.vnet.ibm.com
This is the intended behavior. The HosySystem class is just a placeholder - if the guest has the SBLIM providers installed, then
proper class to represent the host is Linux_ComputerSystem (this is
libvirt-cim-bounces@redhat.com wrote on 2008-09-17 01:54:39: the the
SBLIM provider that represents the "base" or host system).
We don't want the HostSystem provider to return anything in this case, because there's no need for a placeholder.
If the HostSystem provider return NULL, how to make test case work? Because the test expects to return at least one Xen_HostSystem instance. Would you please explain more for me on this? Any suggestion on fixing them?
The test behavior needs to be changed for the sblim case.
1) If SBLIM: Enum of HostSystem doesn't return any instances 2) If not SBLIM: Enum of HostSystem returns a single instance
If Enum of HostSystem doesn't return any instances with sblim base provider installed, how to deal with Host* related test case? The association will return NULL through HostSystem such as HostedResourcePool forward query, then what should we do? Thanks!
If you take a look at the get_host() in Virt_HostSystem.c, you'll get an
understanding of how the providers determine whether a SBLIM instance is
available on the system.
Does this help?
-- 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
The test behavior needs to be changed for the sblim case.
1) If SBLIM: Enum of HostSystem doesn't return any instances 2) If not SBLIM: Enum of HostSystem returns a single instance
If Enum of HostSystem doesn't return any instances with sblim base provider installed, how to deal with Host* related test case? The association will return NULL through HostSystem such as HostedResourcePool forward query, then what should we do?
This will be changed in the future. The problem is that Linux_ComputerSystem lives in a different namespace, so we need to make the association providers handle the different namespaces. In the SBLIM case, you'll want to use Linux_ComputerSystem instead of HostSystem. However, we don't support that yet. I'd add a bug to the cimtest wiki and then have the tests XFAIL in the situation where you need to use Linux_ComputerSystem to resolve an association. -- Kaitlin Rupert IBM Linux Technology Center kaitlin@linux.vnet.ibm.com
libvirt-cim-bounces@redhat.com wrote on 2008-09-18 03:47:56:
The test behavior needs to be changed for the sblim case.
1) If SBLIM: Enum of HostSystem doesn't return any instances 2) If not SBLIM: Enum of HostSystem returns a single instance
If Enum of HostSystem doesn't return any instances with sblim base provider installed, how to deal with Host* related test case? The association will return NULL through HostSystem such as HostedResourcePool forward query, then what should we do?
This will be changed in the future. The problem is that Linux_ComputerSystem lives in a different namespace, so we need to make the association providers handle the different namespaces.
In the SBLIM case, you'll want to use Linux_ComputerSystem instead of HostSystem. However, we don't support that yet. I'd add a bug to the cimtest wiki and then have the tests XFAIL in the situation where you need to use Linux_ComputerSystem to resolve an association.
Then how to verify the test use Linux_ComputerSystem instead of HostSystem in test? One way is to check if sblim base provider is installed, the other way is to check the return instance of enumerate HostSystem. Any other suggestion? Thanks!
-- 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
This will be changed in the future. The problem is that Linux_ComputerSystem lives in a different namespace, so we need to make the association providers handle the different namespaces.
In the SBLIM case, you'll want to use Linux_ComputerSystem instead of HostSystem. However, we don't support that yet. I'd add a bug to the cimtest wiki and then have the tests XFAIL in the situation where you need to use Linux_ComputerSystem to resolve an association.
Then how to verify the test use Linux_ComputerSystem instead of HostSystem in test? One way is to check if sblim base provider is installed, the other way is to check the return instance of enumerate HostSystem. Any other suggestion?
Thanks!
I'd do the following: 1) HostSystem: 01_enum.py - Enum Linux_ComputerSystem - if this call returns an instance, then the enum of HostSystem shouldn't return any instances. Otherwise, you should get back a HostSystem instance. 2) For all other tests the depend on a HostSystem instance, do an enum of HostSystem. If no instances are returned, do an enum of Linux_ComputerSystem and use that instance. Does this help? -- Kaitlin Rupert IBM Linux Technology Center kaitlin@linux.vnet.ibm.com
This will be changed in the future. The problem is that Linux_ComputerSystem lives in a different namespace, so we need to make the association providers handle the different namespaces.
In the SBLIM case, you'll want to use Linux_ComputerSystem instead of HostSystem. However, we don't support that yet. I'd add a bug to
libvirt-cim-bounces@redhat.com wrote on 2008-09-18 23:41:40: the
cimtest wiki and then have the tests XFAIL in the situation where you need to use Linux_ComputerSystem to resolve an association.
Then how to verify the test use Linux_ComputerSystem instead of HostSystem in test? One way is to check if sblim base provider is installed, the other way is to check the return instance of enumerate HostSystem. Any other suggestion?
Thanks!
I'd do the following:
1) HostSystem: 01_enum.py - Enum Linux_ComputerSystem - if this call returns an instance, then the enum of HostSystem shouldn't return any instances. Otherwise, you should get back a HostSystem instance.
Which namespace does Linux_ComputerSystem live in? The enum of Linux_ComputerSystem return NULL: [root@elm** ~]# wbemcli ein http://root:password@localhost/root/virt:Linux_ComputerSystem * * wbemcli: Cim: (5) CIM_ERR_INVALID_CLASS: Linux_ComputerSystem * Since the namespace of Linux_ComputerSystem is different from the others, how to set CIM_NS twice in one test case? That is to say, I have to set CIM_NS as /root/virt when I enum HostSystem, then the namespace have to be set others when I enum Linux_ComputerSystem in one test case. Thanks!
2) For all other tests the depend on a HostSystem instance, do an enum of HostSystem. If no instances are returned, do an enum of Linux_ComputerSystem and use that instance.
Does this help? -- 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
My apologies for not responding to this on Friday.
I'd do the following:
1) HostSystem: 01_enum.py - Enum Linux_ComputerSystem - if this call returns an instance, then the enum of HostSystem shouldn't return any instances. Otherwise, you should get back a HostSystem instance.
Which namespace does Linux_ComputerSystem live in? The enum of Linux_ComputerSystem return NULL:
[root@elm** ~]# wbemcli ein http://root:password@localhost/root/virt:Linux_ComputerSystem * * wbemcli: Cim: (5) CIM_ERR_INVALID_CLASS: Linux_ComputerSystem *
root/virt is the namespace of the libvirt-cim providers. The SBLIM providers live in root/cimv2
Since the namespace of Linux_ComputerSystem is different from the others, how to set CIM_NS twice in one test case? That is to say, I have to set CIM_NS as /root/virt when I enum HostSystem, then the namespace have to be set others when I enum Linux_ComputerSystem in one test case.
This is very similar to what we have to do for the ECTP test cases - RegisteredProfile lives in root/interop, while ComputerSystem lives in root/virt. I'd take a look at those test cases for ideas on how to handle multiple namespaces in one test.
2) For all other tests the depend on a HostSystem instance, do an enum of HostSystem. If no instances are returned, do an enum of Linux_ComputerSystem and use that instance.
ttps://www.redhat.com/mailman/listinfo/libvirt-cim -- Kaitlin Rupert IBM Linux Technology Center kaitlin@linux.vnet.ibm.com
libvirt-cim-bounces@redhat.com wrote on 2008-09-23 04:49:53:
My apologies for not responding to this on Friday.
I'd do the following:
1) HostSystem: 01_enum.py - Enum Linux_ComputerSystem - if this
call
returns an instance, then the enum of HostSystem shouldn't return any instances. Otherwise, you should get back a HostSystem instance.
Which namespace does Linux_ComputerSystem live in? The enum of Linux_ComputerSystem return NULL:
[root@elm** ~]# wbemcli ein http://root:password@localhost/root/virt:Linux_ComputerSystem * * wbemcli: Cim: (5) CIM_ERR_INVALID_CLASS: Linux_ComputerSystem *
root/virt is the namespace of the libvirt-cim providers. The SBLIM providers live in root/cimv2
Thanks! I can enumerate it in root/cimv2 namespace.
Since the namespace of Linux_ComputerSystem is different from the others, how to set CIM_NS twice in one test case? That is to say, I have to set CIM_NS
as
/root/virt when I enum HostSystem, then the namespace have to be set others when I enum Linux_ComputerSystem in one test case.
This is very similar to what we have to do for the ECTP test cases - RegisteredProfile lives in root/interop, while ComputerSystem lives in root/virt.
I'd take a look at those test cases for ideas on how to handle multiple namespaces in one test.
2) For all other tests the depend on a HostSystem instance, do an
enum
of HostSystem. If no instances are returned, do an enum of Linux_ComputerSystem and use that instance.
ttps://www.redhat.com/mailman/listinfo/libvirt-cim
-- 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
participants (2)
-
Guo Lian Yun -
Kaitlin Rupert