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:
When running leapp with LANG=fr_FR.UTF-8, the system is not seen as registered. The message below which inhibits the upgrade is printed in the report:
~~~
Risk Factor: high (inhibitor)
Title: The system is not registered or subscribed.
Summary: The system has to be registered and subscribed to be able to proceed with the upgrade, unless the --no-rhsm option is specified when executing leapp.
Remediation: [hint] Register your system with the subscription-manager tool and attach proper SKUs to be able to proceed the upgrade or use the --no-rhsm leapp option if you want to provide target repositories by yourself.
~~~

Version-Release number of selected component (if applicable):
leapp-repository-0.10.0-2.el7_8.noarch

How reproducible:
100%

Steps to Reproduce:
1. export LANG=fr_FR.UTF-8
2. leapp preupgrade


Additional info:
Exporting LANG=en_US.UTF-8 should easily fix the issue.
The output of subscription being translated, we can't rely on it without forcing the English language.

Thank you Chris for the report. Currently, we have documented that the en_US.UTF-8 locale is required set before the run of leapp (on the whole system or just exported LANG envar when running leapp). See chapter 2, step 7 ("Ensure you have the system locale set to en_US.UTF-8").

But we agreed we could enforce the expected locale inside the leapp to improve user experience. So keeping this opened and we will improve it in future.

To make it more clear, let me summarize the expected output of this ticket:
---
Leapp will enforce the en_US.UTF-8 locale automatically for the IPU, ignoring the locale setup of the system.
---

*** Bug 1961843 has been marked as a duplicate of this bug. ***

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