Uploaded image for project: 'Satellite'
  1. Satellite
  2. SAT-18993

redhat.satellite_operations.installer does not ensure that the satellite RPM is installed

XMLWordPrintable

    • Moderate
    • None

      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.

        There are no Sub-Tasks for this issue.

            egolov@redhat.com Evgeni Golov
            jira-bugzilla-migration RH Bugzilla Integration
            RH Bugzilla Integration RH Bugzilla Integration
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: