Uploaded image for project: 'Satellite'
  1. Satellite
  2. SAT-26095 foreman-maintain backup does not back up container gateway DB
  3. SAT-26104

[QE][AUTOMATION] foreman-maintain backup does not back up container gateway DB

XMLWordPrintable

    • Icon: Sub-task Sub-task
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • 0
    • Phoenix - Content
    • Sprint 136, Sprint 137, Sprint 138, Sprint 139, Sprint 140, Sprint 141, Sprint 142

      Automation should just entail adding the container_gateway to:

      https://github.com/SatelliteQE/robottelo/blob/master/tests/foreman/maintain/test_backup_restore.py#L34-L35

      https://github.com/SatelliteQE/robottelo/blob/master/tests/foreman/maintain/test_backup_restore.py#L33

      Description of problem:

      foreman-maintain backup doesn't take a backup for the container gateway DB. This is true for both the SQLite DB and the new Postgres DB.

      How reproducible:

      100%

      Is this issue a regression from an earlier version:

      No regression, this has been the case since Satellite 6.10.

      Steps to Reproduce:

      1. Populate a smart proxy with container content.

      2. Perform a foreman-maintain backup and restore on the smart proxy.

      Actual behavior:

      The container gateway no longer knows what repositories are synced.

       

      Expected behavior:

      Container content should be immediately consumable after restore.

       

      QE Tracker for https://issues.redhat.com/browse/SAT-26095

              Unassigned Unassigned
              satellite-jira-automation@redhat.com Satellite Jira-Automation
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: