Red Hat Bugzilla – Bug 839709
checkisomd5 should return 0 if the check is aborted
Last modified: 2014-01-10 11:55:28 EST
Description of problem:
In cases where a user manually aborts an image check, the checkisomd5 returns 1. With a recent dracut change, this now causes dracut errors and eventually a panic and failure to boot.
AFAICT, anything that is not a PASS returns 1.
dracut bug: https://bugzilla.redhat.com/show_bug.cgi?id=817419
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.take any iso file
2.run checkisomd5 on the iso
3.abort the run
returns 1, a failure code
returns 0, a successful finish
See also bug 907600 (request for an additional return value for UNKNOWN). These two bugs should be dealt with at the same time.
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '17'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 17's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 17 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged change the
'version' to a later Fedora version prior to Fedora 17's end of life.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
move this to F19
The fix for bug 907600 took care of this by adding 2 for aborted.