Red Hat Bugzilla – Bug 427339
[HTS5.1-18][harness][ia64][EL4] - hts plan giving traceback error
Last modified: 2008-06-23 15:53:13 EDT
Description of problem:
When attempted to test hts-5.1-18 on ia64 system, with RHEL4.6-AS, the command,
hts plan --server <ip of test server>, its given traceback error.
In Past, there was a bug filed almost looks like the same (referenced below),
but, that time, it was found that the system under test was not installed with
dbus packages. As soon as those were installed, the bug fixed.
But this time all the dbus packages are already installed in the system, still
the bug persists.
Previous Bug Reference :- https://bugzilla.redhat.com/show_bug.cgi?id=307081
Dbus packages installed in the system are :-
Version-Release number of selected component (if applicable):
O.S. - RHEL4-U6-AS
Not always, because, the same when I installed in EL4.6 ia64 QE stable systems,
and there it was installed properly without any error, but in another ia64
system, I faced this problem.
Steps to Reproduce:
1. Install hts and dependent packages - dt, stress, lmbench in EL4.6-AS system
2. Execute the command hts plan --server <ip of the test server>
3. Observe the traceback
hts tool not creating the test plans. Giving traceback.
It should create the test plans for that specific system.
Additional info: Traceback error file is attached with this bug.
Created attachment 290720 [details]
hts traceback error file
Is the RHEL 4 U6 install running as a fully-virtualized or para-virtualized guest?
Also, please check that the dbus-deamon is running.
specifically, start haldaemon and messagebus and see if hts plan will run.
After starting haldaemon and messagebus, this problem is fixed.
Fixed in HTS 5.2 R5: added test and error message to check if HAL daemons are
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.