Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-32316

OCP upgrade to 4.14 failed to get VolumeID from volumeMigrationService

XMLWordPrintable

    • Important
    • No
    • False
    • Hide

      None

      Show
      None

      Description of problem:

      Pods using vSphere volumes which were migrated from in-tree to CSI drivers are in init or ContainerCreating status after migration.

      Version-Release number of selected component (if applicable):

      OCP 4.13.37 upgrading to 4.14.19
vCenter version is 7.0.3, apiVersion is 7.0.3.0 and build is 22837322

      How reproducible:

      All the time in customer environment

      Steps to Reproduce:

      1. Have a working OCP 4.13 with vsphere integration.
2. Have workload using legacy in-tree volumes
3. Upgrade OCP to 4.14 version

      Actual results:

      Although all COs moved to the correct version of OCP, core pods, such image-registry and monitoring pods are not starting because they cannot mount the migrated vSphere volumes

      Expected results:

      Migrated volumes should work without issues and pods should be able to start

      Additional info:

            fbertina@redhat.com Fabio Bertinatto
            rhn-support-jcoscia Javier Coscia
            Wei Duan Wei Duan
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: