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

Upgrade from one containerized release to another

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Critical Critical
    • 6.20.0
    • None
    • Installation, Upgrades
    • None
    • Upgrade containerized to next version
    • To Do
    • SAT-40449 - Containerization overflow
    • False
    • sat-rocket
    • None
    • None
    • None

      Goal:

      When a user has deployed a containerized setup they need to be able to upgrade. While downstream this only becomes needed by Satellite 6.20, but upstream this can be tested earlier. It's good to start working on this before we release though because it may influence the design.

      Today we have 2 upgrading guides: connected (6.18) and disconnected (6.18). Both should be prepared.

      Acceptance Criteria:

      • As a user I can deploy a containerized Foreman 3.16 and upgrade it to Foreman 3.17
      • The code is ready to upgrade from Satellite 6.19 to Satellite 6.20, even though that doesn't exist yet
      • There is documentation, at least in upstream

      Open questions:

      • Do we also support upgrading from upstream x.y to nightly and/or downstream 6.19 to stream?
      • How do we go about testing this?

              Unassigned Unassigned
              ekohlvan@redhat.com Ewoud Kohl van Wijngaarden
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: