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:
The RHSCL is detected in a generic 'Red Hat-signed packages are unknown to Leapp':
The use of RHSCL is a common practices and i expected here a dedicated 'Risk' section in the PreUpgrade report including (reference to) instructions how to handle package upgrades from RHSCL packages to their RHEL8 equivalent.
E.g. httpd,php,git have also corresponding RHEL8 module streams and packages. A generic approach can be documented here.
Similar to the KCS article below.
How does RHEL7 to RHEL8 upgrade will affect RHSCL httpd24?
https://access.redhat.com/solutions/4294761
I am not sure it will be possible to give suggestion to all the detected packages every time as version change between RHEL 7 and RHEL 8 for example PHP module available in RHEL 8 is from 7.2 to 7.4 But a generic documentation explaining that this needs to be handled manually would be helpful.
Version-Release number of selected component (if applicable):
leapp-repository-0.14.0-4.el7_9.noarch
How reproducible:
100%
Steps to Reproduce:
1. Install packages from RHSCL repo for example : rh-git227-git php54-php-common
2. Perform leapp preupgrade/upgrade. We can see in the transaction that leapp tries to remove these packages
~~~
Removing dependent packages:
httpd24-libcurl x86_64 7.61.1-2.el7 @System 553 k
php54-php-common x86_64 5.4.40-4.el7 @System 3.8 M
python x86_64 2.7.5-89.el7 @System 79 k
rh-git227-git x86_64 2.27.0-3.el7 @System 368 k
rh-git227-git-core x86_64 2.27.0-3.el7 @System 32 M
rh-git227-git-core-doc noarch 2.27.0-3.el7 @System 12 M
rh-git227-perl-Git noarch 2.27.0-3.el7 @System 63 k
~~~
3.
Actual results:
~~~
Risk Factor: low
Title: Some enabled RPM repositories are unknown to Leapp
Summary: The following repositories with Red Hat-signed packages are unknown to Leapp:
- rhel-server-rhscl-7-rpms
And the following packages installed from those repositories may not be upgraded:
- rh-git227-git-core-doc
- php54-php-common
- php54-runtime
- rh-git227-runtime
- httpd24-libcurl
- httpd24-libnghttp2
- httpd24-runtime
- rh-git227-perl-Git
- rh-git227-git-core
- rh-git227-git
Remediation: [hint] You can file a request to add this repository to the scope of in-place upgrades by filing a support ticket
Key: 8e89e20c645cea600b240156071d81c64daab7ad
~~~
Expected results:
A dedicated risk section showing the RHSCL packages detected and being removed after upgrade and documentation to AppStream repos or instruction for handling them manually.
Additional info:
I think this tie some similarity to this already existing bug it will be helpful to see why the particular packages are removed due to what dependency for these packages too.
https://bugzilla.redhat.com/show_bug.cgi?id=1925103
Some RHSCL are build ontop of the RHSCL provided httpd24-libcurl,httpd24-libnghttp2 packages that are dependent on libssh2 that will be removed.
This implicit removal of many RHSCL packages matches the request in BZ1925103 to provide the user feedback in the preupgrade which deprecated package will impact other non-BaseOS RPMs to be removed.
Comment 35RHEL Program Management
2023-09-12 11:05:49 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 36RHEL Program Management
2023-09-12 11:21:22 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.
Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.
To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:
"Bugzilla Bug" = 1234567
In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Comment 37Red Hat Bugzilla
2024-01-11 04:25:07 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days