Red Hat Bugzilla – Bug 71466
exit code not set
Last modified: 2015-01-07 18:59:13 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.0.0) Gecko/20020530
Description of problem:
up2date does not set the exit code when it gets an error.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. up2date-nox -u
2. If it fails to connect because the service is busy, an error code 51 is
generated, but up2date exits with an exit code of 0.
3. echo $?
Actual Results: 0
Expected Results: 1 or 51
This prevents rational scripting. My script reports success, and later I find
out that it wasn't successful at all because up2date is reporting bogus status.
Status "normal" because the workaround is non-trivial.
*** This bug has been marked as a duplicate of 67163 ***
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.