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.

Bug 2131798

Summary: pulpcore-selinux postinstall script runs fixfiles for wrong rpm
Product: Red Hat Satellite Reporter: Lukas Pramuk <lpramuk>
Component: InstallationAssignee: Odilon Sousa <osousa>
Status: CLOSED ERRATA QA Contact: Lukas Pramuk <lpramuk>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.12.0CC: ehelms, lzap, osousa, rlavi
Target Milestone: 6.15.0Keywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: pulpcore-selinux-2.0.1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-04-23 17:12:42 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 Lukas Pramuk 2022-10-03 17:01:44 UTC
Description of problem:
pulpcore-selinux postinstall script runs fixfiles for wrong rpm - python3-pulpcore
such rpm doesn't exist. There is only python39-pulpcore (python38-pulpcore for 6.11)

/sbin/fixfiles -R python3-pulpcore restore || :

We ship the same pulpcore-selinux rpm into both 6.12 and 6.11 so we cannot just replace python3-pulpcore with python39-pulpcore as this would be still wrong for 6.11

As fixfiles -R doesn't support globbing (*) we have to do something like this:
/sbin/fixfiles -R $(rpm -qa python3*-pulpcore) restore || :


Version-Release number of selected component (if applicable):
6.12.0
pulpcore-selinux-1.3.2-1.el8pc


How reproducible:
deterministic


Steps to Reproduce:
1. Check pulpcore-selinux rpm scripts for wrong "python3-pulpcore"
 # rpm -q --scripts -p pulpcore-selinux | grep python3-pulpcore
/sbin/fixfiles -R python3-pulpcore restore || :
  /sbin/fixfiles -R python3-pulpcore restore || :

Actual results:
-R python3-pulpcore

Expected results:
-R python38-pulpcore (for 6.11)
-R python39-pulpcore (for 6.12)
-R $(rpm -qa python3*-pulpcore) (in order to stay universal, one rpm fits both)

Comment 1 Lukas Pramuk 2024-02-07 15:53:46 UTC
VERIFIED.

@Satellite 6.15.0 Snap 8
pulpcore-selinux-2.0.1-1.el8pc.x86_64

by the reproducer described in comment#0:

# rpm -q --scripts pulpcore-selinux | grep 'python.*-pulpcore'
/sbin/fixfiles -R python3.11-pulpcore restore || :
  /sbin/fixfiles -R python3.11-pulpcore restore || :

>>> pulpcore-selinux postinstall script runs fixfiles for correct rpm - python3.11-pulpcore

Comment 5 errata-xmlrpc 2024-04-23 17:12:42 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.15.0 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-2024:2010