Uploaded image for project: 'Red Hat Fuse'
  1. Red Hat Fuse
  2. ENTESB-18466

Fuse Online automatic upgrade to the latest version via OperatorHub ( across multiple versions )

    XMLWordPrintable

Details

    • Bug
    • Resolution: Won't Do
    • Critical
    • fuse-7.11.1-GA
    • fuse-7.10.1-GA
    • Fuse Online
    • None

    Description

      The Fuse Operator metadata image for 7.10.1 contains these channels:

      Let's say that the user has still the 7.9.3 version of Fuse Online and they choose `latest` update channel. The OCP starts the upgrade plan and first, it spawns Fuse Online 7.10.0 operator. When the operator is ready (which doesn't mean that the upgrade process is done), the OCP starts spawning Fuse Online operator 7.10.1 and deletes Fuse Online operator 7.10.0. The problem is that the 7.10.0 operator can be in the middle of the upgrading process.
      So for now, the user needs to choose the channel where is n+1 version in order to be sure that the upgrade process performs correctly.

      Is there any way in the Operator framework how an operator can say to OCP that the upgrade process is done? ( so the OCP starts spawning the next version only if the FO upgrade process is done not when right after the FO operator is running)

      Additional info in the chat thread: https://chat.google.com/room/AAAAulBShBA/Osoqwe_m0Z4

      Attachments

        1. image.png
          33 kB
          Matej Kralik
        2. Kooha-04-13-2022-15-08-42.mp4
          4.23 MB
          Matej Kralik

        Issue Links

          Activity

            People

              parichar@redhat.com Paul Richardson
              mkralik@redhat.com Matej Kralik
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: