Uploaded image for project: 'OpenShift Service Mesh'
  1. OpenShift Service Mesh
  2. OSSM-8597

3.0.0-tp.1 operator is not automatically upgraded to 3.0.0-tp.2

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Normal Normal
    • OSSM 3.0-TP2
    • None
    • Sail Operator
    • None
    • False
    • None
    • False
    • Release Notes
    • 3.0.0-tp.1 operator is not automatically upgraded to 3.0.0-tp.2. It's necessary to manually remove the old 3.0.0-tp.1 operator and install the new 3.0.0-tp.2 operator. It's not necessary to remove operands (Istio, IstioCNI).

      When the new servicemeshoperator3.v3.0.0-tp.2 is available in the `candidates` channel, existing servicemeshoperator3.v3.0.0-tp.1 is not automatically upgraded. It's necessary to remove servicemeshoperator3.v3.0.0-tp.1 and install servicemeshoperator3.v3.0.0-tp.2.

      Operands can stay and everything continues to work after operator re-installation.

              fbrychta@redhat.com Filip Brychta
              fbrychta@redhat.com Filip Brychta
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: