Red Hat Bugzilla – Bug 72704
RFE: up2date needs to return usable error codes
Last modified: 2008-07-22 11:44:58 EDT
It would be nice if up2date (and I assume rhn_register) both returned error/status codes upon exit. There is no way to scriptically determine the outcome of the process.
I added sys.exit(main() or 0) to up2date's wrapper.py, which helps (i.e., a return code will always be returned. Need to do the same for rhn_register and rhn_check before moving this to MODIFIED.
Note: gtk/glade hijack sys.exit. You can sys.exit whatever you want and gtk/glade will exit with their own exit codes (which is never what you want).
nice two year old bug without a comment from the assignee. status?
From a customer: """ Can you make the return code of up2date be non-zero when RHN is down? $ sudo up2date --showall https://xmlrpc.rhn.redhat.com/XMLRPC IMPORTANT MESSAGE FOLLOWS: Red Hat Network is currently experiencing technical difficulties. We apologize for any inconvenience this outage may cause. Thank you for using Red Hat Network. --the RHN team ksa@rhupdate1 AFS-Admin $ echo $? 0 """ https://enterprise.redhat.com/issue-tracker/?module=issues&action=view&tid=48350 Bumping priority to high for this reason.
RHN needs the following information to be provided by the customer: 1- which version of RHEL are they using? 2- which version of up2date are they using? ... because this problem is not reproducible in any versions of RHEL4. This should thus be removed from the RHEL4.5 blocker list.
User bnackash@redhat.com's account has been closed