This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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 2031870 - redhat.satellite_operations.installer does not ensure that the satellite RPM is installed
Summary: redhat.satellite_operations.installer does not ensure that the satellite RPM ...
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Ansible Collection
Version: 6.10.1
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: stream
Assignee: Evgeni Golov
QA Contact: Satellite QE Team
URL:
Whiteboard:
: 2213032 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-12-13 15:53 UTC by Rodrique Heron
Modified: 2024-06-06 02:17 UTC (History)
3 users (show)

Fixed In Version: satellite-installer-6.15.0.3
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-06-06 02:17:32 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Image of Foreman UI (133.04 KB, image/png)
2021-12-13 15:53 UTC, Rodrique Heron 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   SAT-18993 0 None Migrated None 2024-06-06 02:17:31 UTC

Description Rodrique Heron 2021-12-13 15:53:30 UTC 
Created attachment 1846106 [details]
Image of Foreman UI

Description of problem:

Using the redhat.satellite_operations.installer role results in the Foreman UI or perhaps foreman being deployed instead of Satellite. 

Ran the playbook against a fresh install of RHEL 7 with only the required Satellite repos enabled. At the completion of the play, I go log into Satellite, and instead, I see the foreman UI. The version displayed on the log-in page is Version 2.5.2.18. 

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

satellite_operations: 0.3.2
satellite-installer-6.10.0.7-1.el7sat.noarch


How reproducible:

Define vars:

satellite_installer_scenario: satellite
satellite_installer_options:
  - '--foreman-initial-admin-password {{ rodhouse_admin_pass }}'
  - '--foreman-initial-admin-username {{ sat_user_vault }}'
  - '--foreman-initial-organization ACME'
  - '--foreman-initial-location Brooklyn'
  - '--foreman-proxy-content-enable-katello-agent=true'
  - '--foreman-proxy-dns-managed=false'
  - '--foreman-proxy-dhcp-managed=false'


Include the role:
- include_role:
    name: redhat.satellite_operations.installer


Actual results:

Satellite installation completes but foreman is deployed instead of Satellite.

Expected results:

Satellite to be installed.
Comment 1 Eric Helms 2021-12-13 17:53:49 UTC 
The root of the problem is the satellite RPM does not get pulled in which then pulls in our branding plugin (foreman_theme_satellite). While we work on fixing this, this can be worked around by setting "satellite_installer_package: satellite".
Comment 2 Rodrique Heron 2021-12-13 23:20:01 UTC 
Also looks like satellite_installer_package in redhat/satellite_operations/roles/installer/defaults/main.yml defaults to the satellite-installer as the package.

satellite_installer_command: satellite-installer
satellite_installer_package: satellite-installer
satellite_installer_verbose: true
satellite_installer_no_colors: false
satellite_installer_options: []
Comment 3 Brad Buckingham 2023-01-04 22:48:23 UTC 
Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team.  Thank you.
Comment 5 Evgeni Golov 2023-06-07 13:56:09 UTC 
Workaround for those affected: dnf install satellite && satellite-installer

Background: the collection, right now, does not install the meta package (satellite) and the system is thus lacking the rubygem-foreman_theme_satellite package. The workaround will install that and the installer will make sure any migrations etc are ran.
Comment 6 Eric Helms 2023-06-13 18:53:47 UTC 
*** Bug 2213032 has been marked as a duplicate of this bug. ***
Comment 8 Eric Helms 2024-06-06 02:17:32 UTC 
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Note You need to log in before you can comment on or make changes to this bug.