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

Satellite restore operation fails during satellite-installer run (Foreman API 500 / Capsule 9090 connection refused)

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • 6.19.0
    • Backup and Restore
    • None
    • None
    • None
    • None

      Description of problem:

      Satellite restore operation fails during the satellite-installer phase after successful database restore and file extraction.

      The restore proceeds successfully through:

      • DB connectivity checks
      • Dropping and restoring PostgreSQL databases (Foreman, Candlepin, Pulpcore)
      • Extracting pulp data

      Failure occurs during installer-run, where the installer fails to register the Foreman host due to a 500 Internal Server Error from the Foreman API.

      How reproducible:

      always, 100%

      Is this issue a regression from an earlier version:

      Yes

      Steps to Reproduce:
      1. Enable puppet on the satellite
      2. create a backup of different types
      3. check that appropriate files are created
      4. restore the backup
      Actual behavior:

      • satellite-installer fails with exit status 6.
      • Foreman API returns 500 Internal Server Error during host lookup.
      • Restore scenario fails at step [installer-run].

       

      Expected behavior:
      restore succeeds
      Business Impact / Additional info:

       

              egolov@redhat.com Evgeni Golov
              rh-ee-napathak Nakul Pathak
              Nakul Pathak
              Nakul Pathak Nakul Pathak
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: