GY> Did you run it on
elm3b197.beaverton.ibm.com in KVM mode? I ran
GY> it on your machine(elm3b197.beaverton.ibm.com) in KVM mode and
GY> add comments inline.
No, this was on my own machine.
> > ElementCapabilities - 05_hostsystem_cap.py: FAIL
> > CIM_ERR_NOT_FOUND: The requested object could not be found: "No
> such instance"
>
GY> It fails because of missing argument, I fixed it already.
Where/when was it fixed? This was with the latest tree at the time.
> > 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
>
GY> Also passed during my test.
Well, this is clearly a syntax bug of some kind that is in need of
some additional exception handling. It happens a *lot*, so it should
be easy to track down.
This was on a F9 beta machine, so perhaps a new version of Python is
causing some differing behavior.
--
Dan Smith
IBM Linux Technology Center
Open Hypervisor Team
email: danms(a)us.ibm.com