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

LVMS: LVMCluster without any valid optionalPaths remains in "Progressing" instead of "Failed" state

XMLWordPrintable

    • Low
    • No
    • 2
    • OCPEDGE Sprint 245, OCPEDGE Sprint 246
    • 2
    • False
    • Hide

      None

      Show
      None
    • LVMClusters can now correctly determine a failed state if there are no valid optionalPaths in the deviceSelector
    • Bug Fix
    • In Progress

      When running the polarion test case https://polarion.engineering.redhat.com/polarion/#/project/OSE/workitem?id=OCP-67003 then we currently have a failure in the build candidate.

      This is because of https://github.com/openshift/lvm-operator/blob/main/internal/controllers/vgmanager/devices.go#L189-L198 triggering a failure, but this doesnt result in a failed status update: https://github.com/openshift/lvm-operator/blob/main/internal/controllers/vgmanager/controller.go#L205-L208

      Instead its just reconciled again resulting in the failing test case

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

              Created:
              Updated:
              Resolved: