Hide Forgot
Description of problem ====================== If `preupg --riskcheck` is ran before `preupg`, it exits with status 255. This is not a documented exit status, thus could be misinterpreted by scripting tools, resulting in hidden problems. Version-Release number of selected component ============================================ preupgrade-assistant-2.1.5-4.el6.noarch How reproducible ================ Always Steps to Reproduce ================== 1. Have a fresh install, or remove /root/preupgrade* directories 2. DON'T run `preupg` but run `preupg --riskcheck` 3. Observe exit status Actual results ============== Exit status is 255, which is not a documented value (preupg --help) Expected results ================ Exit with one of documented values (currently 0-2).
Note that I have seen preupg --riskcheck exit with 255 also in other circumstances related to broken modules. I have not been able to reproduce it reliably, though. Hopefully once we'll have custom module set (bug 1289977 comment 1), we'll be able to catch that again. (That would be another ticket than this one, though.)
This is fixed by upstream commit https://github.com/upgrades-migrations/preupgrade-assistant/commit/7914abcc88a391757a746287adde9b3b1639204a
preupgrade-assistant-ui-2.1.10-5.el6.noarch: [0 root@qeos-115 ~]# preupg --riskcheck; echo $? The 'preupg' command was not run yet. Run it to check for possible risks. 24 [0 root@qeos-115 ~]#
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2016-2616.html