[Libvirt-cim] Test report on KVM

Deepti B Kalakeri deeptik at linux.vnet.ibm.com
Tue Apr 8 09:28:57 UTC 2008 


Kaitlin Rupert wrote:
> Dan, I see basically the same results you see.  Except I see log 
> entries for the failing tests.
>
> This is on a system with the following:
>
> F8
> xen-3.1.0-13.fc8
> libvirt-0.4.1-3.fc9
>
> I did a clone of the cimtest tree and the provider tree.  I also have 
> a KVM guest defined.
>
>>  > > ElementCapabilities - 01_forward.py: FAIL
>>  > > CIM_ERR_NOT_FOUND: The requested object could not be found: "No
>>  > such instance (CreationClassName)"
>>    It passed during my test.
>
> This failed for me.  There's definitely a test case problem.  The 
> offending code:
>
>             elec = assoc.AssociatorNames(options.ip,
>                                          "ElementCapabilities",
>                                          "ComputerSystem",
>                                          options.virt,
>                                          Name = system,
>                                          CreationClassName = 
> "Xen_ComputerSystem")
>
> The CreationClassName shouldn't be hardcoded to Xen_ComputerSystem.
>
>>     > > ElementCapabilities - 05_hostsystem_cap.py: FAIL
>>  > > CIM_ERR_NOT_FOUND: The requested object could not be found: "No
>>  > such instance"
>>  >
>>    It fails because of missing argument, I fixed it already.
>
> This test passes for me.  It looks like Daisy's fix for this went into 
> the tree sometime earlier today.
>
>>  >
>>  > > ElementConforms - 01_forward.py: FAIL
>>  > > ElementConforms - 02_reverse.py: FAIL
>>  >
>>  > The log:
>>  >
>>  > > ====01_forward.py Log====
>>  > > 1. Property values for CIM:DSP1057-VirtualSystem-1.0.0a and domain
>>  > Domain-0 is
>>  > > EnabState = 2 EnabDefault = 2 ReqSt = 12
>>  > > 2. Values for CIM:DSP1042-SystemVirtualization-1.0.0 and host
>>  > guaranine.danplanet.com is
>>  > > EnabState = 5 EnabDefault = 2 ReqSt = 12
>>  > > ====02_reverse.py Log====
>>  >
>>  > The lack of a log for 02 is troubling.
>
> I get a log here.  I see:
>
> Mon, 24 Mar 2008 14:51:57:TEST LOG:INFO         -  ====02_reverse.py 
> Log====
> Mon, 24 Mar 2008 14:51:59:TEST LOG:ERROR        -  Failed to get 
> associators information for RegisteredProfile
> Mon, 24 Mar 2008 14:51:59:TEST LOG:ERROR        -  Exception: 
> u'KVM_ComputerSystem'
>
> It is troubling that you didn't see any log output during your run.
>
>>  >
>>  > > HostSystem - 02_hostsystem_to_rasd.py: FAIL
>>  > > Traceback (most recent call last):
>>  > >   File "/usr/lib64/python2.5/logging/__init__.py", line 744, in 
>> emit
>>  > >     msg = self.format(record)
>>  > >   File "/usr/lib64/python2.5/logging/__init__.py", line 630, in 
>> format
>>  > >     return fmt.format(record)
>>  > >   File "/usr/lib64/python2.5/logging/__init__.py", line 418, in 
>> format
>>  > >     record.message = record.getMessage()
>>  > >   File "/usr/lib64/python2.5/logging/__init__.py", line 288, in 
>> getMessage
>>  > >     msg = msg % self.args
>>  > > TypeError: not enough arguments for format string
>>  >
>>   Also passed during my test.
>
> This fails for me.  In addition to the python errors, I see the 
> following in the log:
>
> ERROR:TEST LOG:AllocationUnits Mismatch
> ERROR:TEST LOG:Mistmatching association values
>
> I think there's a few testcase issues here:
>
> 1) In XenKvmLib/rasd.py:
>
> Globals.logger.error("Returned %s instead of %s or %s", \
>               assoc_info['AllocationUnits'], 
> memrasd_list['AllocationUnits'])
>
> The string takes 3 arguments, but only 2 are given.  The third 
> argument should be removed.
I had sent a patch for this On March26 *"Fixing: The syntax error and 
the removing the extra parameter in certain functions"* , for the 
arguments problem.
I dont find this in the tree yet.
>
> 2) I think HostSystem - 02_hostsystem_to_rasd.py needs to be updated 
> to reflect the recent provider change.  The provider returns KiloBytes 
> as the unit, but the test is expecting MegaBytes.
>
>>
>>  > Looks like a testcase error.
>>  >
>>  > > RASD - 01_verify_rasd_fields.py: FAIL
>>  >
>>  > No log for this one either.
>
> I see the following in the log:
>
> TEST LOG:ERROR        -  Define or start domain failed
>
>>  >
>>  > > RASD - 02_enum.py: FAIL
>>  > > Traceback (most recent call last):
>>  > >   File "/usr/lib64/python2.5/logging/__init__.py", line 744, in 
>> emit
>>  > >     msg = self.format(record)
>>  > >   File "/usr/lib64/python2.5/logging/__init__.py", line 630, in 
>> format
>>  > >     return fmt.format(record)
>>  > >   File "/usr/lib64/python2.5/logging/__init__.py", line 418, in 
>> format
>>  > >     record.message = record.getMessage()
>>  > >   File "/usr/lib64/python2.5/logging/__init__.py", line 288, in 
>> getMessage
>>  > >     msg = msg % self.args
>>  > > TypeError: not enough arguments for format string
>>  >
>>  > Same as above.
>>   Also passed during my running test.
>
> This failed for me.
>
>>  >
>>  > > SettingsDefine - 01_forward.py: FAIL
>>  > > SettingsDefine - 02_reverse.py: FAIL
>>  > > SettingsDefine - 03_sds_fwd_errs.py: FAIL
>>  >
>>  > No log.
>
> I got log messages for these 3 tests.
>
>>  >
>>  > > SystemDevice - 01_forward.py: FAIL
>>  >
>>  > Log:
>>  >   > > ====01_forward.py Log====
>>  > > Examined test_domain/00:11:22:33:44:55
>>  > > Examined test_domain/mem
>>  > > Examined test_domain/xvdb
>>  > > Examined test_domain/0
>>  >
>>  > > SystemDevice - 03_fwderrs.py: FAIL
>>  > > Traceback (most recent call last):
>>  > >   File "/usr/lib64/python2.5/logging/__init__.py", line 744, in 
>> emit
>>  > >     msg = self.format(record)
>>  > >   File "/usr/lib64/python2.5/logging/__init__.py", line 630, in 
>> format
>>  > >     return fmt.format(record)
>>  > >   File "/usr/lib64/python2.5/logging/__init__.py", line 418, in 
>> format
>>  > >     record.message = record.getMessage()
>>  > >   File "/usr/lib64/python2.5/logging/__init__.py", line 288, in 
>> getMessage
>>  > >     msg = msg % self.args
>>  > > TypeError: not all arguments converted during string formatting
>>  >
>>  > This is repeated a bunch of times, but I've snipped them out.
>>  >
>>  > > VSSD - 04_vssd_to_rasd.py: FAIL
>>  > > Traceback (most recent call last):
>>  > >   File "/usr/lib64/python2.5/logging/__init__.py", line 744, in 
>> emit
>>  > >     msg = self.format(record)
>>  > >   File "/usr/lib64/python2.5/logging/__init__.py", line 630, in 
>> format
>>  > >     return fmt.format(record)
>>  > >   File "/usr/lib64/python2.5/logging/__init__.py", line 418, in 
>> format
>>  > >     record.message = record.getMessage()
>>  > >   File "/usr/lib64/python2.5/logging/__init__.py", line 288, in 
>> getMessage
>>  > >     msg = msg % self.args
>>  > > TypeError: not enough arguments for format string
>>  >
>>  > Seems to be a common issue.
>>  >
>>  > > VirtualSystemManagementService - 05_destroysystem_neg.py: FAIL
>>  >
>>  > Log:
>>  >
>>  > > destroy_fail>>nonexistent: Got expected return code 4
>>  > > destroy_fail>>nonexistent: Got expected return code 4
>>  >
>>  > > VirtualSystemMigrationSettingData - 01_enum.py: FAIL
>>  >
>>  > No log.
>
> ERROR:TEST LOG:ClassName Mismatch
> ERROR:TEST LOG:Returned Xen_VirtualSystemMigrationSettingData instead 
> of KVM_VirtualSystemMigrationSettingData
>
>>  >
>>  > > VirtualSystemSnapshotServiceCapabilities - 01_enum.py: FAIL
>>  >
>>  > No log.
>
> ERROR:TEST LOG:ClassName Mismatch
> ERROR:TEST LOG:Returned Xen_VirtualSystemSnapshotServiceCapabilities 
> instead of KVM_VirtualSystemSnapshotServiceCapabilities
>

More information about the Libvirt-cim mailing list