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

Upon creation LVMCluster CR goes into 'Failed' state, later updates to 'Ready'

XMLWordPrintable

    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • 1
    • Moderate
    • None
    • None
    • Rejected
    • OCPEDGE Sprint 257
    • 1
    • In Progress
    • Release Note Not Required
    • None
    • None
    • None
    • None
    • 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:

       On fresh cluster when LVMCLuster CR is created, it goes into 'Failed' state first then updates to 'Ready'.

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

       4.17.0-27

      Steps to Reproduce:

      1. Install LVMS 4.17.0 from operatorHub
2. Proceed to create LVMCluster CR
3. Observe that while LVMCluster getting generated it goes into 'Failed' state
4. If successfully created then gets updated to 'Ready' state

      Actual results:

      While LVMCluster getting generated it goes into 'Failed' state

      Expected results:

      While LVMCluster getting generated it goes into 'Progressing' state

      Additional info:

              rh-ee-jmoller Jakob Moeller (Inactive)
              rh-ee-rdeore Rahul Deore
              None
              None
              Rahul Deore Rahul Deore
              None
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: