Bug 2031870
| Summary: | redhat.satellite_operations.installer does not ensure that the satellite RPM is installed | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Rodrique Heron <rheron> | ||||
| Component: | Ansible Collection | Assignee: | satellite6-bugs <satellite6-bugs> | ||||
| Status: | NEW --- | QA Contact: | Satellite QE Team <sat-qe-bz-list> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 6.10.1 | CC: | ddf-bot, egolov, ehelms | ||||
| Target Milestone: | Unspecified | Keywords: | Triaged, WorkAround | ||||
| Target Release: | Unused | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | Type: | --- | |||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
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". 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: [] 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. 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. *** Bug 2213032 has been marked as a duplicate of this bug. *** |
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.