Bug 2043299

This bug has been reported fixed in a new RHCOS build and is ready for QE verification.  To mark the bug verified, set the Verified field to Tested.  This bug will automatically move to MODIFIED once the fix has landed in a new bootimage.

Preverify passed with RHCOS 49.84.202201262103-0 according to steps in https://bugzilla.redhat.com/show_bug.cgi?id=2043296#c2, can get failure message on the console when using rhcos-49.84.202201212103-0-qemu.x86_64.qcow2

The fix for this bug has landed in a bootimage bump, as tracked in bug 2043298 (now in status MODIFIED).  Moving this bug to MODIFIED.

Verify passed using rhcos-49.84.202206151501-0-qemu.x86_64.qcow2

Steps to verify:

Prepare ignition config using command:
$ butane -o 2043299.ign -r -p -s 2043299.bu

$ cat 2043299.bu
variant: fcos
version: 1.4.0
storage:
  disks:
  - device: /dev/vdb
    wipe_table: true
    partitions:
    - number: 1
  luks:
  - name: disk1
    device: /dev/vdb1
    key_file:
      inline: mykey
  filesystems:
  - device: /dev/disk/by-id/dm-name-disk1
    format: xfs
    path: /var/mnt/encrypted_test
    with_mount_unit: true
systemd:
  units:
    - name: serial-getty
      dropins:
      - name: autologin-core.conf
        contents: |
          [Service]
          # Override Execstart in main unit
          ExecStart=
          # Add new Execstart with `-` prefix to ignore failure`
          ExecStart=-/usr/sbin/agetty --autologin core --noclear %I $TERM

============================================
1. Create snapshot of a RHCOS 4.9 image
qemu-img create -f qcow2 -F qcow2 -o backing_file=rhcos-49.84.202206151501-0-qemu.x86_64.qcow2 rhcos-49.84.202206151501-0-qemu.x86_64.hhei.qcow2 16G

2. Create an empty qcow2 disk to use as a secondary disk
qemu-img create -f qcow2 2043299.qcow2 5G

3. Set variables
VM_NAME=rhcos49
VCPUS=2
RAM_MB=4096
IMAGE=/home/fedora/data/rhcos-49.84.202206151501-0-qemu.x86_64.hhei.qcow2
LUKS_DISK=/home/fedora/data/2043299.qcow2
IGNITION_CONFIG=/home/fedora/data/ign/2043299.ign

4. Run the virt-install command
virt-install --connect="qemu:///system" --name="${VM_NAME}" --vcpus="${VCPUS}" --memory="${RAM_MB}" --import --disk path="${IMAGE}",format=qcow2,bus=virtio --disk path="${LUKS_DISK}",format=qcow2,bus=virtio --qemu-commandline="-fw_cfg name=opt/com.coreos/config,file=${IGNITION_CONFIG}" --os-variant rhel8.4 --graphics=none

5. Confirm initial install was successful
6. Destroy/undefine the VM
virsh destroy "${VM_NAME}" && virsh undefine "${VM_NAME}"

7. Delete + recreate the root disk

rm "${IMAGE}"

qemu-img create -f qcow2 -F qcow2 -o backing_file=rhcos-49.84.202206151501-0-qemu.x86_64.qcow2 ${IMAGE} 16G

8. Re-run virt-install
virt-install --connect="qemu:///system" --name="${VM_NAME}" --vcpus="${VCPUS}" --memory="${RAM_MB}" --import --disk path="${IMAGE}",format=qcow2,bus=virtio --disk path="${LUKS_DISK}",format=qcow2,bus=virtio --qemu-commandline="-fw_cfg name=opt/com.coreos/config,file=${IGNITION_CONFIG}" --os-variant rhel8.4 --graphics=none

9. Observe a succesfull install + reuse of the secondary disk
[core@localhost ~]$ df -Th | grep mnt
/dev/mapper/disk1 xfs       5.0G   68M  5.0G   2% /var/mnt/encrypted_test

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (OpenShift Container Platform 4.9.40 bug fix update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2022:5180