Uploaded image for project: 'OpenShift Virtualization'
  1. OpenShift Virtualization
  2. CNV-33811

documenation for storage configuration of in-guest LVM is missing.

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • None
    • CNV v4.12.0, CNV v4.13.0
    • CNV Documentation, CNV Storage
    • None
    • False
    • Hide

      None

      Show
      None
    • True
    • Release Notes
    • CNV-29991 - 4.15 Tech Debt
    • No
    • Hide
      Virtual machines that use Logical volume management (LVM) with block storage devices require additional configuration to avoid conflicts with Red Hat Enterprise Linux CoreOS (RHCOS) host.
      Workaround: Create a VM, provision LVM, restart VM. This creates an empty system.lvmdevices file. (https://issues.redhat.com/browse/OCPBUGS-5223)
      Show
      Virtual machines that use Logical volume management (LVM) with block storage devices require additional configuration to avoid conflicts with Red Hat Enterprise Linux CoreOS (RHCOS) host. Workaround: Create a VM, provision LVM, restart VM. This creates an empty system.lvmdevices file. ( https://issues.redhat.com/browse/OCPBUGS-5223 )
    • Known Issue
    • Proposed
    • ---
    • ---
    • Yes
    • 2
    • Storage Core Sprint 247, Storage Core Sprint 248

      Description of problem:

      This bug is for documenting the In-guest LVM configuration require additional configuration in CNV 4.13 and earlier. The actual problem is understood and fixed in OCP 4.14

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

      OCP 4.13
OCP 4.12

      How reproducible:

      Always

      Steps to Reproduce:

      1. Use classic storage provision like FC or iSCSI that mounts LUNs on RHCOS worker.
2. Any in-guest LVM configuration.
3. additional configuration is needed for "lvmdevices" on the worker node.

      Actual results:

      Without extra configuration, RHCOS attempts to activate LVM devices, and causes VM problems.

      Expected results:

      RHCOS leaves the LVM volumes alone.

      Additional info:

      This problems is well known.

[OCPBUGS-5223] Pod stuck in terminating if there is an LVM LogicalVolume on the underlying block PVC - Red Hat Issue Tracker

https://issues.redhat.com/browse/OCPBUGS-5223

The fix is to use "lvmdevices', this is automatic in OCP 4.14, but must be manually configured in OCP 4.12 and OCP 4.13.

Chapter 11. Limiting LVM device visibility and usage
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html/configuring_and_managing_logical_volumes/limiting-lvm-device-visibility-and-usage_configuring-and-managing-logical-volumes

            dclowers@redhat.com Daniel Clowers
            rh_pelauter@redhat.com Peter Lauterbach
            Jenia Peimer Jenia Peimer
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: