Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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
======================
It's possible to generate assessment without upgrade path installed at /usr/share, but it's not possible to use --riskcheck to verify this assessment: preupg will complain that upgrade path is not installed and exit with status 20.
Version-Release number of selected component
============================================
preupgrade-assistant-2.1.9-1.el6
How reproducible
================
Always
Steps to Reproduce
==================
1. Create a custom upgrade path
2. Run preupg with this path (--contents parameter)
3. Run preupg --riskcheck --verbose
Actual results
==============
Error is printed:
There were no contents found in directory /usr/share/preupgrade. If you would like to use this tool, you have to install some
and exit status is 20.
Expected results
================
No error
Additional info
===============
Note that --riskcheck (and other modes) documentation does not mention way to specify *which* result to check, so there's an underlying assumption that it's always the last one.
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://access.redhat.com/errata/RHBA-2017:3211
Description of problem ====================== It's possible to generate assessment without upgrade path installed at /usr/share, but it's not possible to use --riskcheck to verify this assessment: preupg will complain that upgrade path is not installed and exit with status 20. Version-Release number of selected component ============================================ preupgrade-assistant-2.1.9-1.el6 How reproducible ================ Always Steps to Reproduce ================== 1. Create a custom upgrade path 2. Run preupg with this path (--contents parameter) 3. Run preupg --riskcheck --verbose Actual results ============== Error is printed: There were no contents found in directory /usr/share/preupgrade. If you would like to use this tool, you have to install some and exit status is 20. Expected results ================ No error Additional info =============== Note that --riskcheck (and other modes) documentation does not mention way to specify *which* result to check, so there's an underlying assumption that it's always the last one.