Red Hat Bugzilla – Bug 279011
change from sysreport to sosreport breaks hardware certification
Last modified: 2008-08-02 19:40:35 EDT
Description of problem: We are seeing this warning when running the hts test suite: cp: cannot stat `this': No such file or directory This was seen just as it was finishing up running "hts certify --test memory" on an ia64 full-virt guest. The test run was otherwise successful. Here is the message in more context: Creating compressed archive... Your sosreport has been generated and saved in: /tmp/sosreport-hp_fv_1-356410-ff7197.tar.bz2 The md5sum is: 628a0fe97d54fb0477d64b24e5ff7197 Please send this file to your support representative. cp: cannot stat `this': No such file or directory + rpm -ql kernel-2.6.18-43.el5 Checking kernel Ok. ...finished running ./info.sh, exit code=0 recovered exit code=0 hts-report-result info PASS /var/log/hts/runs/1/info/output.log saveOutput: /var/log/hts/runs/1/info/output.log Return value was 0 Version-Release number of selected component (if applicable): hts-5.0-50.el5 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
This error occurs because sysreport was replaced by sosreport in RHEL 5.1, breaking HTS's integration, as it's looking for the archive the tool produces based on specific prompts. Moving bug over to the RHEL Beta product, as the old prompts should be supported.
Looks like the same problem I addressed with the latest re-spin in RHEA-2007:0855. See BZ#294771. Please the candidate for errata (sos-1.7-9.1.el5) http://brewweb.devel.redhat.com/brew/rpminfo?rpmID=1032624 Thanks. -- Navid
Errata candidate RPM can be found here: http://porkchop.devel.redhat.com/brewroot/packages/sos/1.7/9.1.el5/noarch/sos-1.7-9.1.el5.noarch.rpm -- Navid
This BZ is in needinfo state however I am unable to see any question. it appears there are several private comments which I cannot see. If you have a question for me please make that comment non-private.
opened comments #5 and #4 for Doug marco
Doug, this bz appears to be a duplicate of bug 294771 but we'd like you to verify that before we CLOSED/DUP this bug.
(In reply to comment #8) > Doug, this bz appears to be a duplicate of bug 294771 but we'd like you to > verify that before we CLOSED/DUP this bug. I updated to the latest sos as described in comment #5 and it does indeed fix the issue I was hitting. I will close this BZ as a dup. *** This bug has been marked as a duplicate of 294771 ***