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

Satellite upgrade fails to set template capsule for satellite managed subnet

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • 6.11.0
    • Upgrades
    • Moderate
    • None

      Description of problem:

      After upgrade to 6.11, Satellite was unable to set template capsule for satellite server managed subnet. Satellite server not listed. However, Capsule server automatically picked up the configuration on upgrade.

      Additionally, satellite stopped listening on port 8000

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

      How reproducible:
      Unknown

      Steps to Reproduce:
      1. Follow upgrade documentation for Satellite
      2. Follow upgrade documentation for Capsule

      Actual results:
      Post upgrade, satellite not available as template server for satellite managed subnet.
      Post upgrade, capsule automatically configured for capsule managed subnet.

      Expected results:

      Satellite server automatically configured appropriately for managed subnets.

      Additional info:
      Satellite was unable to define template capsule for subnet managed by the Satellite after upgrade. Capsule automatically picked up the configuration.

      Satellite stopped listening on port 8000 so provisioning failed.
      These were resolved by re-running installer with:

      satellite-installer --scenario=satellite --foreman-proxy-templates=true --foreman-proxy-template-url=http://sat6.parmstrong.ca:8000 --foreman-proxy-http=true

            jira-bugzilla-migration RH Bugzilla Integration
            parmstro@redhat.com Paul Armstrong
            RH Bugzilla Integration RH Bugzilla Integration
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: