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 2130871 - Settings states Foreman instead of Satellite in some entries
Summary: Settings states Foreman instead of Satellite in some entries
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Settings
Version: 6.12.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: 6.14.0
Assignee: nalfassi
QA Contact: visawant
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-09-29 08:53 UTC by Ladislav Vasina
Modified: 2023-11-08 14:18 UTC (History)
9 users (show)

Fixed In Version: foreman-3.7.0, rubygem-foreman_theme_satellite-12.0.0.4-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-11-08 14:18:02 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 36088 0 Normal Closed Settings states Foreman instead of Satellite in some entries 2023-05-23 15:01:23 UTC
Red Hat Issue Tracker SAT-15082 0 None None None 2023-01-24 18:01:45 UTC
Red Hat Issue Tracker SAT-15278 0 None None None 2023-05-29 12:38:33 UTC
Red Hat Product Errata RHSA-2023:6818 0 None None None 2023-11-08 14:18:20 UTC

Description Ladislav Vasina 2022-09-29 08:53:03 UTC
Description of problem:
In the satellite settings, there are many entries stating Foreman instead of Satellite.
The entries sometimes state Satellite in the name column but in the description column, there is Foreman (sometimes there is just Foreman in a place where I think Satellite should be). I think that this should be consistent and we should use Satellite in settings entries.

Version-Release number of selected component (if applicable):
satellite-6.12.0-3.el8sat.noarch
foreman-3.3.0.8-1.el8sat.noarch

How reproducible:
every time

Steps to Reproduce:
1. Go to satellite settings and see entries from the list below. In these entries, I think we should change Foreman to Satellite.
##############################################################
List of settings entries where I have found inconsistencies:
##############################################################
Settings>General>Satellite URL
Settings>General>Entries per page
Settings>General>Capsule request timeout
Settings>General>Append domain names to host
Settings>General>Satellite UUID
Settings>General>New host details UI

Settings>RHCloud>Include parameters in insights-client repos

Settings>Authentication>OAuth active
Settings>Authentication>OAuth map users
Settings>Authentication>Failed login attempts limit
Settings>Authentication>SSL certificate
Settings>Authentication>SSL CA file
Settings>Authentication>SSL private key
Settings>Authentication>Server CA file
Settings>Authentication>Websockets SSL key
Settings>Authentication>Websockets SSL certificate

Settings>Email>Email reply address

Settings>Provisioning>Host owner
Settings>Provisioning>Query local nameservers
Settings>Provisioning>Update IP from built request
Settings>Provisioning>Use short name for VMs
Settings>Provisioning>Clean up failed deployment
Settings>Provisioning>Destroy associated VM on host delete
Settings>Provisioning>Manage PuppetCA
Settings>Provisioning>USE UUID certificates

Settings>Facts>Create new host when fats are uploaded
Settings>Facts>Update hostgroup from facts
Settings>Facts>Update subnets from facts

Settings>Config Management>Create new host when report is uploaded
Settings>Config Management>Matchers inheritance
Settings>Config Management>Default parameters lookup path
Settings>Config Management>Interpolate ERB in parameters

Settings>Ansible>Default verbosity level
Settings>Ansible>Post-provision timeout
Settings>Ansible>Default Ansible inventory report template

Settings>Template Sync>Commit message
##############################################################

Actual results:
Foreman is stated instead of Satellite

Expected results:
Satellite should be stated instead of Foreman

Additional info:
The same problem is happening in Satellite 6.11

Comment 3 nalfassi 2023-02-13 13:23:04 UTC
Created redmine issue https://projects.theforeman.org/issues/36088 from this bug

Comment 5 Bryan Kearney 2023-05-23 18:21:56 UTC
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/36088 has been resolved.

Comment 7 visawant 2023-06-01 11:57:57 UTC
Failed QA

Version tested: Satellite 6.14.0 Snap 2.0

Comment 10 visawant 2023-07-13 11:26:24 UTC
Failed QA
Version tested: Satellite 6.14.0 Snap 7.0
Reason: Partially fixed

Comment 12 visawant 2023-07-30 16:59:30 UTC
Verified.

Version: Satellite 6.14.0 Snap 9

Comment 15 errata-xmlrpc 2023-11-08 14:18:02 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.14 security and bug fix update), 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:6818


Note You need to log in before you can comment on or make changes to this bug.