LVMCluster fails to found storage device link

Solution Verified - Updated -

Issue

  • 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.
  • 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.

Environment

  • Red Hat OpenShift Container Platform (RHOCP)
    • 4.17
  • LVM Storage Operator (LVMS)
    • 4.17.0
    • 4.17.1

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content