Uploaded image for project: 'MicroShift'
  1. MicroShift
  2. USHIFT-1455

When an upgrade from 4.13 to (fake) 4.15 is attempted, it should be blocked

XMLWordPrintable

    • Strategic Product Work
    • False
    • Hide

      None

      Show
      None
    • False
    • OCPSTRAT-310 - MicroShift updateability for GA
    • uShift Sprint 239

      Looking at the code I think we wouldn't catch that currently because according to current implementation: if the version doesn't exist, the no comparison is made and it proceeds to writing current executable's version to the file

      https://github.com/openshift/microshift/blob/928d4f3a6ec051a78f2d0de3f11c52d2c1d827ef/pkg/admin/prerun/version.go#L36

              rh-ee-dhensel Douglas Hensel
              pmatusza@redhat.com Patryk Matuszak
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: