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 2149895 - foreman-maintain and its dependant gems are installed in EL8 gems path for Sat6.11 on EL7
Summary: foreman-maintain and its dependant gems are installed in EL8 gems path for Sa...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Packaging
Version: 6.11.0
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Lukas Pramuk
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-12-01 10:46 UTC by Gaurav Talreja
Modified: 2022-12-02 21:57 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-12-02 21:57:46 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SAT-14147 0 None None None 2022-12-01 15:20:02 UTC

Description Gaurav Talreja 2022-12-01 10:46:43 UTC 
Description of problem:
foreman-maintain and its dependant gems are installed in EL8 gems path of /usr/share/gems/gems , for Sat6.11 on EL7 where earlier gems path was /opt/theforeman/tfm/root/usr/share/gems/gems/

Version-Release number of selected component (if applicable):
satellite-6.11.4.1-1.el7sat.noarch

How reproducible:
Always

Steps to Reproduce:
1. # ls /usr/share/gems/gems
bigdecimal-1.2.0  clamp-1.1.2  foreman_maintain-1.0.18  highline-2.0.3  io-console-0.4.2  json-1.7.7  psych-2.0.0  rdoc-4.0.0

2. # ls /opt/theforeman/tfm/root/usr/share/gems/gems/
3.

Actual results:
foreman-maintain and its dependant gems are installed in EL8 gems path for EL7 Satellite

Expected results:
foreman-maintain and its dependant gems are installed in EL7 gems path for EL7 Satellite

Additional info:
Comment 2 Patrick Creech 2022-12-02 21:57:46 UTC 
This is expected.  rubygem-foreman_maintain is not built against the software collection on el7, but against the system provided ruby.  This is true for every rubygem-foreman_maintain build I have checked.  This was done intentionally, due to the nature of rubygem-foreman_maintain and ensuring that it will work without the need to install satellite components, as it is the tool you use to install/maintain satellite.
Note You need to log in before you can comment on or make changes to this bug.