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

neither documentation nor migration-stats tell customers that /var/lib/pulp/media may grow to large sizes during the migration

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • 6.9.7
    • Documentation
    • None
    • 0
    • False
    • Moderate
    • None
    • None
    • None
    • None

      Document URL:

      https://access.redhat.com/documentation/en-us/red_hat_satellite/6.10/html/upgrading_and_updating_red_hat_satellite/upgrading_red_hat_satellite#Upgrading_Server_upgrade-guide

      Section Number and Name:

      3.1. Upgrading Satellite Server
      Before You Begin

      Describe the issue:

      The documentation warns customers that /var/lib/pulp/published/ may double in size during the migration, but it doesn't tell customers that docker images will be moved to /var/lib/pulp/media, that this directory could become large, or how to predict the eventual size of that directory. This isn't mentioned by the output of the command "satellite-maintain content migration-stats" either.

      This issue affects customers who have mounted volumes at /var/lib/pulp/published rather than at /var/lib/pulp, because in this case /var/lib/pulp/media will spill over into the /var volume.

      Suggestions for improvement:

      • mention that docker images will be moved to /var/lib/pulp/media
      • give customers a command to evaluate how much storage their docker images take up on disk prior to the migration

              mdolezel@redhat.com Marie Hornickova
              jira-bugzilla-migration RH Bugzilla Integration
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: