Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-45180

[RHEL10] "Kickstart insufficient": LUKS doesn't work with lvm and --grow

XMLWordPrintable

    • python-blivet-3.10.0-9.el10
    • None
    • Moderate
    • rhel-sst-storage-management
    • ssg_filesystems_storage_and_HA
    • 10
    • 12
    • 2
    • False
    • Hide

      None

      Show
      None
    • Yes
    • None
    • Bug Fix
    • Hide
      Cause:
      When users specifies `--size=1` together with `--grow` and --encrypted` in kickstart file for a new device the installer fails to correctly grow the device to a valid size for an encrypted device.

      Consequence:
      The automated installation stops with "kickstart insufficient" error and user intervention is required to proceed with the installation.

      Fix:
      Processing of growable devices in kickstart was adjusted to always correctly set the device size required to proceed with installation even when `--size=1` is requested as starting point for size grow.

      Result:
      Installation is successfully started with the device specified in kickstart with `--size=1 --grow --encrypted` and proceeds without errors and manual intervention required.
      Show
      Cause: When users specifies `--size=1` together with `--grow` and --encrypted` in kickstart file for a new device the installer fails to correctly grow the device to a valid size for an encrypted device. Consequence: The automated installation stops with "kickstart insufficient" error and user intervention is required to proceed with the installation. Fix: Processing of growable devices in kickstart was adjusted to always correctly set the device size required to proceed with installation even when `--size=1` is requested as starting point for size grow. Result: Installation is successfully started with the device specified in kickstart with `--size=1 --grow --encrypted` and proceeds without errors and manual intervention required.
    • Proposed
    • None

      Description of problem:
      Kickstart using LVM partitioning with LUKS does not accept the --grow option

      How reproducible:
      Always

      Steps to Reproduce:
      1. Kickstart using LUKS and LVM with a partition using --grow

      Actual results:
      "Kickstart insufficient" "('device cannot be smaller than 16 MiB', 'luks5'

      Expected results:
      Partition is created exactly as when not using LUKS

      Additional info:
      logvol /opt --name=lv_opt --vgname=vg_rocsoft --size=1 --grow --fsoptions="nodev" --encrypted --cipher=aes-cbc-essiv:sha256 --passphrase=xxxxxx

              vtrefny@redhat.com Vojtěch Trefný
              jira-bugzilla-migration RH Bugzilla Integration
              Vojtěch Trefný Vojtěch Trefný
              Release Test Team Release Test Team
              Valentina Ashirova Valentina Ashirova
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated: