Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite 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 "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. 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 "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-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.
In "Chapter 5. Upgrading Hosts to Next Major Red Hat Enterprise Linux Release" under the "Prerequisites" section,
* The first two points would usually cover what preparation users have to do on their systems that are to be leapp'ed and then we point to the RHEL docs and then in the RHEL, docs we have the information about leapp metadata mentioned.
For better user experience, I believe we should mention the point in our satellite doc as a fifth point under the "Prerequisites" section,
~~~
You must obtain and deploy Leapp metadata manually on all the systems where RHEL conversion would take place. For more information, see [Leapp utility metadata in-place upgrades of RHEL for disconnected upgrades](https://access.redhat.com/articles/3664871).
~~~
Do you know the version where they have been added to the package?
We should mention it in the docs, that since the version x.y.z these steps are not required.