The above test case passes with false positive. The existing test case is intended to verify for exception when a wrong Name is passed as a parameter. _ For ex: without the sblim-base-provider the tc would be checking_ wbemcli ain -ac Xen_HostedService 'http://root:p@localhost:5988/root/virt:Xen_HostSystem.CreationClassName="Xen_HostSystem",Wrong="wrong"'
* * wbemcli: Cim: (6) CIM_ERR_NOT_FOUND: No such instance (Name) *
_But with the sblim-base-provider installed the tc would be checking_
wbemcli ain -ac Xen_HostedService 'http://root:P@localhost:5988/root/virt:Xen_HostSystem.CreationClassName="Linux_ComputerSystem",Wrong="wrong"'
* * wbemcli: Cim: (6) CIM_ERR_NOT_FOUND: No such instance (CreationClassName) *
These are really good points Deepti - thanks for taking a look at this.
though getting the exception for Linux_ComputerSystem in the second case is valid for now, as the query with the Linux_CS does not work yet, but this is not the expected behavior of the test case.
The tc just verifies only "No such instance " string which is present in both the exceptions and hence passes. 1) This test cannot be supported to work with sblim-base-provider installed yet.
It can return an XFAIL in the case where the SBLIM providers are installed.
2) We need to update the tc to verify the case where we pass Invalid CreationClassName. 3) We need to be verifying the complete exception instead of just verifying part of it.
-- Kaitlin Rupert IBM Linux Technology Center kaitlin@linux.vnet.ibm.com