RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

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