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

[LVMS] After OCP multi-node upgrade LVMCluster CR stuck in 'Progressing' state

XMLWordPrintable

    • Low
    • No
    • 2
    • OCPEDGE Sprint 252
    • 1
    • False
    • Hide

      None

      Show
      None
    • Release Note Not Required
    • In Progress

      This is an LVMS Bug Report:

      Please create & attach a must-gather as indicated by this Guide to collect LVMS relevant data from the Cluster (linked to the latest version, use older versions of the documentation for older OCP releases as applicable

      Please make sure that you describe your storage configuration in detail. List all devices that you plan to work with for LVMS as well as any relevant machine configuration data to make it easier for an engineer to help out.

      Description of problem:

      [LVMS] After OCP multi-node upgrade, existing LVMClsuter CR stuck in 'Progressing' state

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

      LVMS 4.14.3

      Steps to Reproduce:

      1. Install LVMS operator 4.14.3 on OCP multi-node cluster successfully
2. Upgrade OCP 4.14 to 4.15 successfully
3. Check LVMCluster CR status on upgraded OCP cluster
4. LVMCluster CR stuck in 'Progressing' state

      Actual results:

      LVMCluster CR stuck in 'Progressing' state

      Expected results:

      LVMCluster CR goes into 'Running' state

      Additional info:

      LVMS resource pods are observed to be in 'Running' state, only lvmCluster CR is in 'Progressing' state.

            sakbas@redhat.com Suleyman Akbas
            rh-ee-rdeore Rahul Deore
            Rahul Deore Rahul Deore
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated: