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.
DescriptionAvinash Kulkarni
2021-04-26 14:22:50 UTC
Description of problem:
leapp preupgrade command is failing on the on the rhel-7.9 client registered to Red Hat Satellite 6.8 when simple content access is enabled & even after applying RHBA-2021:0569 as mentioned in Bug 1873312
Version-Release number of selected component (if applicable):
Satellite 6.8.0
RHEL 7.9
How reproducible:-
100%
Actual results:
leapp preuprade should be successful after applying RHBA-2021:0569 as per the Bug 1873312.
leapp preupgrade is failing with error :
Upgrade has been inhibited due to the following problems:
1. Inhibitor: The system is not registered or subscribed.
Consult the pre-upgrade report for details and possible remediation.
Steps to Reproduce:
1. Use SCA enabled manifest on the Satellite server.
2. Sync RHEL-7 and RHEL 8.2 repositories on the Satellite server
3. Register RHEL-7 client with the Satellite server, enable required repositories and perform #yum update.
4. Install leapp & leapp-repository packages
5. # leapp preupgrade
Actual results:
Expected results:
After attaching the subscription to the host, leapp preupgrade should be successful.
Additional info:
@Avinash Kulkarni, would you be able to provide logs from the system please? It is in "/var/log/leapp" + output of the following commands:
# echo $LANG
# rpm -qa | grep leapp
Thanks...
Can you please share the report file? Or can you tell us whether the `subscription status` exit with the non-zero status? It seems as bug in RHSM.
This could be relevant:
https://access.redhat.com/solutions/5060001
I'm not using Satellite but am seeing similar behavior.
Versions:
RHEL ALT 7.6 @s390x
leapp-0.12.0-1.el7_9.noarch
leapp-repository-0.13.0-2.el7_9.noarch
The preupgrade fails and blocks upgrade.
The failing actor is 'scan_subscription_manager_info': "[...] Command ['subscription-manager', 'status'] failed with exit code 1. [...]"
The status is similar to the one reported for Satellite in https://access.redhat.com/solutions/5060001
"
# subscription-manager status
+-------------------------------------------+
System Status Details
+-------------------------------------------+
Overall Status: Unknown
Content Access Mode is set to Organization/Environment Access. This host has access to content, regardless of subscription status.
"
My SKU is not associated to any organization, I just used my customer portal login, which seems to mean that it's Simple Content Access Mode. I confirmed that I have active subscriptions (attached pools successfully).