Bug 1978160

Summary: [RFE] leapp should have a dedicated Risk section for RHSCL repo and packages
Product: Red Hat Enterprise Linux 7 Reporter: Ameya Patil <amepatil>
Component: leapp-repositoryAssignee: Leapp Notifications Bot <leapp-notifications-bot>
Status: NEW --- QA Contact: upgrades-and-conversions
Severity: low Docs Contact:
Priority: low    
Version: 7.9CC: amkulkar, fkrska, jbreitwe, jcastran, jorton, mkluson, peter.vreman, podvody, pstodulk
Target Milestone: rcKeywords: FutureFeature
Target Release: ---Flags: pstodulk: needinfo? (podvody)
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1818077, 1818088    

Description Ameya Patil 2021-07-01 08:41:59 UTC
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

Comment 7 Peter Vreman 2021-07-01 09:44:49 UTC
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.