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:
If a leapp upgrade attempt from RHEL7.6 to RHEL8 fails, subscription-manager reports that the system is unregistered. The system must then be re-registered with RHSM.
Worth noting that this happens with multiple kinds of leapp failure. I observed this behaviour after:
============================================================
ERRORS
============================================================
2019-04-23 18:56:15.249035 [ERROR] Actor: prepare_upgrade_transaction Message: Cannot find any required target repository. The list of available required repositories is empty.
============================================================
END OF ERRORS
============================================================
and
============================================================
ERRORS
============================================================
2019-04-23 18:51:38.848719 [ERROR] Actor: prepare_upgrade_transaction Message: Cannot get release setting. A Leapp Command Error occurred.
============================================================
END OF ERRORS
============================================================
How reproducible:
RHEL7.6 VM, registered directly to RHSM.
Actual results:
Run a leapp upgrade which fails, then check subscription status:
[root@localhost ~]# subscription-manager list --installed
+-------------------------------------------+
Installed Product Status
+-------------------------------------------+
Product Name: Red Hat Enterprise Linux Server
Product ID: 69
Version: 7.6
Arch: x86_64
Status: Not Subscribed
Status Details:
Starts:
Ends:
Expected results:
Run a leapp upgrade which fails, then check subscription status:
[root@localhost ~]# subscription-manager list --installed
+-------------------------------------------+
Installed Product Status
+-------------------------------------------+
Product Name: Red Hat Enterprise Linux Server
Product ID: 69
Version: 7.6
Arch: x86_64
Status: Subscribed
Status Details:
Starts: 01/04/19
Ends: 31/03/20
Additional info:
This occurs in the same manner on both leapp-0.6.0 and latest leapp-0.7.0 versions. As well as latest 0.7.0-1 version, I also tested on:
leapp-0.6.0-1.201904110917Z.ac3f6a7.master.el7_6.noarch.rpm
leapp-0.7.0-0.201904181545Z.ec8ba0a.fix_specfile.PR496.el7_6.noarch.rpm
Hi Russel,
it's known issue. In my case the behaviour you described is same even when there is not fail in the preparation phase (just when you run `rhsm list` on the original RHEL 7 system after run of leapp).
Kevin, you tried that time ago and it worked. Would you check it whether it is broken again or whether it is something related to configuration of system?
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-2020:1959
Description of problem: If a leapp upgrade attempt from RHEL7.6 to RHEL8 fails, subscription-manager reports that the system is unregistered. The system must then be re-registered with RHSM. Worth noting that this happens with multiple kinds of leapp failure. I observed this behaviour after: ============================================================ ERRORS ============================================================ 2019-04-23 18:56:15.249035 [ERROR] Actor: prepare_upgrade_transaction Message: Cannot find any required target repository. The list of available required repositories is empty. ============================================================ END OF ERRORS ============================================================ and ============================================================ ERRORS ============================================================ 2019-04-23 18:51:38.848719 [ERROR] Actor: prepare_upgrade_transaction Message: Cannot get release setting. A Leapp Command Error occurred. ============================================================ END OF ERRORS ============================================================ How reproducible: RHEL7.6 VM, registered directly to RHSM. Actual results: Run a leapp upgrade which fails, then check subscription status: [root@localhost ~]# subscription-manager list --installed +-------------------------------------------+ Installed Product Status +-------------------------------------------+ Product Name: Red Hat Enterprise Linux Server Product ID: 69 Version: 7.6 Arch: x86_64 Status: Not Subscribed Status Details: Starts: Ends: Expected results: Run a leapp upgrade which fails, then check subscription status: [root@localhost ~]# subscription-manager list --installed +-------------------------------------------+ Installed Product Status +-------------------------------------------+ Product Name: Red Hat Enterprise Linux Server Product ID: 69 Version: 7.6 Arch: x86_64 Status: Subscribed Status Details: Starts: 01/04/19 Ends: 31/03/20 Additional info: This occurs in the same manner on both leapp-0.6.0 and latest leapp-0.7.0 versions. As well as latest 0.7.0-1 version, I also tested on: leapp-0.6.0-1.201904110917Z.ac3f6a7.master.el7_6.noarch.rpm leapp-0.7.0-0.201904181545Z.ec8ba0a.fix_specfile.PR496.el7_6.noarch.rpm