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

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

Linking RHIVOS CVEs to...Migration: Automation ...SWIFT: POC ConversionSync from "Extern...XMLWordPrintable

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

      None

      Show
      None
    • Yes
    • None
    • Bug Fix
    • Hide
      .The Kickstart file now correctly sets the required device size for installation when using LVM partitioning with LUKS

      Before this update, when you specified the `--size=1 --grow --encrypted` option in the Kickstart file for a new device, the installer failed to correctly expand the encrypted device to a valid size. Consequently, the automated installation stopped with an error message, for example:
      ----
      "Kickstart insufficient" "('device cannot be smaller than 16 MiB', 'luks5'
      ----
      You would then have to proceed with manual installation without the Kickstart file.

      With this update, the installation starts successfully with the device specified in the Kickstart file with `--size=1 --grow --encrypted`. As a result, the installation proceeds without errors.
      Show
      .The Kickstart file now correctly sets the required device size for installation when using LVM partitioning with LUKS Before this update, when you specified the `--size=1 --grow --encrypted` option in the Kickstart file for a new device, the installer failed to correctly expand the encrypted device to a valid size. Consequently, the automated installation stopped with an error message, for example: ---- "Kickstart insufficient" "('device cannot be smaller than 16 MiB', 'luks5' ---- You would then have to proceed with manual installation without the Kickstart file. With this update, the installation starts successfully with the device specified in the Kickstart file with `--size=1 --grow --encrypted`. As a result, the installation proceeds without errors.
    • Done
    • None
    • 57,005

      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
              Valentina Ashirova
              Vojtěch Trefný Vojtěch Trefný
              Release Test Team Release Test Team
              Angana Chakraborty Angana Chakraborty
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: