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

LVMCluster CR stuck in 'Progressing' state, after cluster is re-installed on custom namespace

XMLWordPrintable

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

      None

      Show
      None

      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:

      LVMCluster CR stuck in 'Progressing' state, after cluster is re-installed on custom namespace

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

      4.15.0-64

      Steps to Reproduce:

      1. Install LVMS operator on default namespace 'openshift-storage'
2. LVMCluster CR 'Running' successfully
3. Un-install LVMS operator and all related resource are deleted
4. Create new custom namespace as per steps in polarion tc: https://polarion.engineering.redhat.com/polarion/#/project/OSE/workitem?id=OCP-68406
5. Re-install LVMS operator on custom namespace
6. Check LVMCluster CR stuck in 'Progressing' state

      Actual results:

      LVMCluster CR stuck in 'Progressing' state

      Expected results:

       LVMCluster CR goes into 'Running' state and LVMS gets installed successfully

      Additional info:

       

            rh-ee-jmoller Jakob Moeller
            rh-ee-rdeore Rahul Deore
            Rahul Deore Rahul Deore
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: