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

[release-4.17] LVMCluster fails to found storage device link

XMLWordPrintable

    • None
    • 0
    • OCPEDGE Sprint 262
    • 1
    • False
    • Hide

      None

      Show
      None
    • Hide
      Before this fix, LVMS excluded all the devices specified by the user via paths or optionalPaths fields if there is a non-existing device configured on the top of the list. After this fix, LVMS correctly determines the state of a specified device and includes it in the volume group creation.
      Show
      Before this fix, LVMS excluded all the devices specified by the user via paths or optionalPaths fields if there is a non-existing device configured on the top of the list. After this fix, LVMS correctly determines the state of a specified device and includes it in the volume group creation.
    • Bug Fix
    • In Progress

      This is a clone of issue OCPBUGS-43910. The following is the description of the original issue:

      Description of problem:

      If the device path on the first line of .spec.deviceClasses.deviceSelector.optionalPaths in the LVMCluster spec is not found, an error occurs, and any devices listed on the second line and after are not recognized.
      
      In a high-availability cluster, the LVMSOperator is installed, and the additional disk's device links by path on each node are added to .spec.deviceClasses.deviceSelector.optionalPaths. When device links are different on each node, adding multiple lines should allow LVMs to recognize each node’s device link, creating a volume group accordingly. However, based on testing in version 4.17, if the device path in the first line is not found on the node, it fails with an error and does not attempt to recognize any devices listed on the second line or later.
      
      Please see the first comment on this ticket for more details on the testing conducted.
      
      The .spec.deviceClasses.deviceSelector.optionalPaths setting is intended to support different device paths on multiple nodes. Due to this bug, it is not possible to deploy a single deviceClass with different device paths across multiple nodes.
      
          

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

      4.17
          

      How reproducible:

          Everytime

      Steps to Reproduce:

          1. attach a disk to nodes
          2. install LVMsOperator
          3. state the multi-line .spec.deviceClasses.deviceSelector.optionalPaths
          

      Actual results:

      Failed
          

      Expected results:

      Ready
          

      Additional info:

          

              sakbas@redhat.com Suleyman Akbas
              openshift-crt-jira-prow OpenShift Prow Bot
              Minal Pradeep Makwana Minal Pradeep Makwana
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: