Bug 2107758

Summary: [RFE] Upgrade to Redis 6
Product: Red Hat Satellite Reporter: vivek singh <vivsingh>
Component: InstallationAssignee: Eric Helms <ehelms>
Status: CLOSED ERRATA QA Contact: Jameer Pathan <jpathan>
Severity: medium Docs Contact:
Priority: high    
Version: 6.11.0CC: ahumbe, aperotti, dalley, dsynk, ehelms, gpayelka, hartsjc, jpathan, peter.vreman, rcavalca, saydas
Target Milestone: 6.13.0Keywords: FutureFeature, PrioBumpGSS, Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-05-03 13:21:28 UTC 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:

Description vivek singh 2022-07-15 22:18:46 UTC
Description of problem: Insights report shows EOL redis version after installing fresh satellite 6.11 


Version-Release number of selected component (if applicable): 6.11 


How reproducible:


Steps to Reproduce:
1. Install Fresh satellite 6.11 
2. check redis version 


Actual results: redis installed of EOL version 
--> redis.x86_64       5.0.3-5.module+el8.4.0+12927+b9845322


Expected results: redis should be installed of latest version 
---> redis.x86_64      6.0.9-5.module+el8.4.0+12929+1bb0d2aa


Additional info: 

[ This is due to redis module stream 5 is marked as default ] 

# dnf module list | grep redis
redis                5 [d][e]        common [d]                               Redis persistent key-value database                                 
redis                6               common [d]                               Redis persistent key-value database                                                                                                                                                                        

~~~~
# yum module provides redis-5.0.3-5.module+el8.4.0+12927+b9845322.x86_64
redis-5.0.3-5.module+el8.4.0+12927+b9845322.x86_64
Module   : redis:5:8040020211011074037:522a0ee4:x86_64
Profiles : common
Repo     : rhel-8-for-x86_64-appstream-rpms
Summary  : Redis persistent key-value database

# yum module provides redis-6.0.9-5.module+el8.4.0+12929+1bb0d2aa.x86_64
redis-6.0.9-5.module+el8.4.0+12929+1bb0d2aa.x86_64
Module   : redis:6:8040020211011082941:522a0ee4:x86_64
Profiles : common
Repo     : rhel-8-for-x86_64-appstream-rpms
~~~~

[ Our installer code just ensures the package is installed ]

~~~~~
# cat /usr/share/foreman-installer/modules/redis/manifests/install.pp
# @summary This class installs the application.
# @api private
class redis::install {
  if $redis::manage_package {
    package { $redis::package_name:
      ensure => $redis::package_ensure,
    }
  }
}
~~~~~

Which translates to running the following command in satellite installer log (which defaults to installing a package from module stream version 5)

# Executing: '/bin/dnf -d 0 -e 1 -y install redis'

Comment 6 Daniel Alley 2022-10-11 15:43:52 UTC
For what it's worth, Pulp already runs using Redis 6 in non-Satellite environments today. So as far as we're concerned there's nothing blocking using Redis 6, even in current releases.

Comment 7 Daniel Alley 2022-10-11 15:45:19 UTC
That is to say, we're not aware of any issues that would prevent you from using Redis 6 for even Satellite 6.12

Comment 9 Jameer Pathan 2023-02-07 12:55:45 UTC
Verified:

Verified with:
- Satellite 6.13.0 snap 9

Test steps:
1. Install Fresh satellite 6.12
2. Upgrade Satellite to 6.13
3. Check redis version 


Observation:
- Satellite is using Redis 6

# rpm -q redis
redis-6.2.7-1.module+el8.7.0+15197+cc495aeb.x86_64

Comment 12 errata-xmlrpc 2023-05-03 13:21:28 UTC
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 (Important: Satellite 6.13 Release), 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/RHSA-2023:2097