Description of problem: When Tested hts-5.1.1 on EL4-U6 for i386 arch, its given Traceback Error!! output.log, info files are attached with this bug as .tar file. Version-Release number of selected component (if applicable): hts-5.1.1 Tree used : EL4-U6-20070927.0 How reproducible: Reproduced once with one try. Steps to Reproduce: 1. 2. 3. Actual results: It is giving traceback error Expected results: Its should PASS. Additional info:
Created attachment 215521 [details] i386-cdrom-tar file
is dbus-python installed? if so, this is a duplicate. Here's the traceback, for easy reference: Running ./cdrom.py: lshal version 0.4.2 block.device = '/dev/hdb' (string) Traceback (most recent call last): File "./cdrom.py", line 692, in ? returnValue = test.do(sys.argv) File "/usr/share/hts/lib/hts/test.py", line 226, in do return self.run() File "./cdrom.py", line 550, in run features = self.configDeviceHAL(cdromDevice,cdromDeviceUDI) File "./cdrom.py", line 133, in configDeviceHAL cdromDevice = hal.getDevice(cdromUDI) File "/usr/share/hts/lib/hts/hal.py", line 29, in getDevice return Device(Constants.hal, self.getDeviceProperties(udi)) File "/usr/share/hts/lib/hts/hal.py", line 39, in getDeviceProperties return self.__GetDevice(udi).GetAllProperties() File "/usr/share/hts/lib/hts/hal.py", line 32, in __GetDevice dev_obj=self.bus.get_object('org.freedesktop.Hal',udi) AttributeError: SystemBus instance has no attribute 'get_object' ...finished running ./cdrom.py, exit code=1
I meant, if it's NOT installed, this bug is a duplicate
I think, for EL4-U6, the client systems for archs i386 and x86_64 requires dbus-python to generate the test plan for the hts. If, so, then, I think, the system was dbus-python package installed, otherwise, it would not generate the test plan even, following which I tested cdrom and other testing. I can not confirm this, because, I used reserved system for this test. But at the same time, when I read through the results.xml file output for cdrom testing, i found the same traceback as you mentioned here in this bug. So, now, please decide, whether its duplicate bug or a new one. :) Otherwise, I need to retest once again to find out if the package installation status!
*** This bug has been marked as a duplicate of 313501 ***