Red Hat Bugzilla – Bug 173844
CDROM test shows failures when doing cdrom and dvd tests together
Last modified: 2007-04-18 13:34:34 EDT
Description of problem:
Found that when running the CDROM test against a combo drive (cdrom,dvd) package
failures are noted when the DVD portion runs the md5sum check.
The reason for this is:
given this hardware.conf entry: CDROM sda(cdrom,dvd)
the test executes like this:
1. create /tmp/rhr/CDROM/device and /tmp/rhr/CDROM/tmp
2. mount CDROM device (w/ CD media) to ./device
3. cp -av ./device/RedHat/RPMS/* ./tmp
4. do md5sum on ./tmp/* and compare (using md5sum -c) to ./device/RedHat/RPMS/*
5. umount cdrom and ask user to swap in a dvd
6. mount dvd to ./device
7. cp -av ./device/RedHat/RPMS/* ./tmp
8. same as step 4 above
9. umount ./device
10. rm -f ./device ./tmp
The problem falls between the cdrom reader and dvd reader tests. Since the
files in ./tmp are not cleaned up prior to the dvd reader test, the files from
the cd reader test are still present, and if they are not overwritten when the
dvd reader test copies files to ./tmp, the md5sum check will result in failures.
I have attached patch files with changes to /usr/share/rhr/tests/CDROM and
/usr/share/rhr/tests/cdrom/functions that fix this. Probably not the more
elegant or even permenant solution, but they DO fix the issue.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.see above. especially visible if you use a RHEL4 x86 cdrom and a RHEL4 U2
x86_64 dvd or some other similar mix.
The RHR suite says PASSED, but the logs show failed pacakge checksums during dvd
Temp directories should be cleaned up between passes to prevent this kind of
thing from happening. Also, the summary should not say PASS if words like
FAILED and WARNING are present in the log file.
Additional info:see attached patches.
Created attachment 121315 [details]
patch to /usr/share/rhr/tests/CDROM
Created attachment 121316 [details]
patch to /usr/share/rhr/tests/cdrom/functions
Recent changes to the CDROM test should fix this problem.
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 the 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.