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.

Bug 2002347

Summary: Leapp error message is not precise
Product: Red Hat Enterprise Linux 7 Reporter: Gleb Galkin <ggalkin>
Component: leapp-repositoryAssignee: Leapp team <leapp-notifications>
Status: CLOSED ERRATA QA Contact: Martin KlusoĊˆ <mkluson>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.9CC: bsanford, jpretori, mkluson, mmacura, pstodulk
Target Milestone: rcFlags: pm-rhel: mirror+
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: leapp-repository-0.15.0-1.el7_9 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-11-10 09:13:09 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Gleb Galkin 2021-09-08 15:23:16 UTC
Description of problem:

Connected bug: https://bugzilla.redhat.com/show_bug.cgi?id=2002077

It would be nice to leapp to make error report more precise and show wrong repoid.

It would save the time of troubleshooting for customers and reduce the load of Red Hat support.

Comment 3 Petr Stodulka 2021-09-08 16:56:42 UTC
Thank you for opening the BZ. I will appreciate a feedback on the change I did in the following PR:
    https://github.com/oamg/leapp-repository/pull/715

Here is my run & error output how it looks with the proposed change:

------------------------------------------------
# leapp preupgrade --debug --enablerepo some-repoid --enablerepo rhel-8-for-x86_64-baseos-rpms --enablerepo rhel-8-for-x86_64-appstream-rpm
.... 
============================================================
                           ERRORS                           
============================================================

2021-09-08 18:45:32.936527 [ERROR] Actor: target_userspace_creator
Message: Some required custom target repositories are not available.
Summary:
    Missing_custom_repositories: "some-repoid", "rhel-8-for-x86_64-appstream-rpm"
    Hint:  The most probably you are using custom or third party actor that produces CustomTargetRepository message or you did a typo in one of repoids specified on command line for the leapp --enablerepo option. Inside the upgrade container, we are not able to find such repository inside any repository file. Consider use of the custom repository file regarding the official upgrade documentation or check whether you did not do a typo in any repoids you specified for the --enablerepo option of leapp. Check the leapp logs to see the list of all available repositories.

============================================================
                       END OF ERRORS                        
============================================================


------------------------------------------------

Is it helpful in this way or do you have any ideas how to improve it?

Comment 6 Petr Stodulka 2021-10-20 11:22:35 UTC
The changes have been merged in the upstream and will be part of the next release. The final solution is different from the one proposed earlier, see the link for details:
    https://github.com/oamg/leapp-repository/pull/731

In short, the error messages have been changed converted to report inhibitors and the report summary contains more info about discovered problems. An example of new reporting:

(stdout)
~~~
# leapp preupgrade --enablerepo nonexistingrepoid
...
============================================================
                     UPGRADE INHIBITED                      
============================================================

Upgrade has been inhibited due to the following problems:
    1. Inhibitor: Some required custom target repositories have not been found
Consult the pre-upgrade report for details and possible remediation.

============================================================
                     UPGRADE INHIBITED                      
============================================================
...
~~~

(report)
~~~
Risk Factor: info (inhibitor)
Title: Some required custom target repositories have not been found
Summary: This can happen when a repository ID was entered incorrectly either while using the --enablerepo option of leapp, or in a third party actor that produces a CustomTargetRepositoryMessage.
The following repositories IDs could not be found in the target configuration:
- nonexistingrepoid

Remediation: [hint] Consider using the custom repository file, which is documented in the official upgrade documentation. Check whether a repository ID has been entered incorrectly with the --enablerepo option of leapp. Check the leapp logs to see the list of all available repositories.
Key: 4970f35ea29b02fb3aaec309a5880dc1402df199
~~~

Comment 11 errata-xmlrpc 2021-11-10 09:13:09 UTC
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 (leapp, leapp-repository, and cockpit-leapp bug fix and enhancement update), 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-2021:4603