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

When MicroShift starts, data and health info are present, but version metadata is missing it should treat the data as 4.13 (proceed with migration/running)

XMLWordPrintable

    • Strategic Product Work
    • False
    • Hide

      None

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

      Scenario:

      • /var/lib/microshift exists
      • /var/lib/microshift/version is missing
      • /var/lib/microshift-backups/health.json exists

      How MicroShift could end up in this situation:
      system rolled back to 4.13, backup was manually restored from /var/lib/microshift-backups/4.13/, but health.json was not deleted.

      https://github.com/openshift/microshift/pull/1957/files#diff-e78e17834c76663b756393d04ebe7aceb8ea4059d44b7d2ae3ee4e9999aead6eR180-R185

              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: