#3313 Issue closed: testing-farm:fedora-39-x86_64 issue with the backup & recovery tests

Labels: enhancement, ReaR Project

gdha opened issue at 2024-09-06 13:58:

  • ReaR version ("/usr/sbin/rear -V"): master branch

  • OS version ("cat /etc/os-release" or "lsb_release -a" or "cat /etc/rear/os.conf"): Fedora 39

  • ReaR configuration files ("cat /etc/rear/site.conf" and/or "cat /etc/rear/local.conf"):

OUTPUT=ISO
SSH_FILES=no
FIRMWARE_FILES=( no )
BACKUP=NETFS
BACKUP_URL=iso:///backup
OUTPUT_URL=null
USER_INPUT_TIMEOUT=10
# 4gb backup limit
PRE_RECOVERY_SCRIPT=("mkdir /tmp/mnt;" "mount /dev/nvme0n1p5 -o subvol=/root /tmp/mnt/;" "modprobe brd rd_nr=1 rd_size=2097152;" "dd if=/tmp/mnt/var/lib/rear/output/rear-ip-172-31-31-150.iso of=/dev/ram0;" "umount /tmp/mnt/;")
ISO_FILE_SIZE_LIMIT=4294967296
ISO_DEFAULT=automatic
ISO_RECOVER_MODE=unattended

  • Hardware vendor/product (PC or PowerNV BareMetal or ARM) or VM (KVM guest or PowerVM LPAR): vm

  • System architecture (x86 compatible or PPC64/PPC64LE or what exact ARM device): x86_64

  • Firmware (BIOS or UEFI or Open Firmware) and bootloader (GRUB or ELILO or Petitboot): UEFI

  • Storage (local disk or SSD) and/or SAN (FC or iSCSI or FCoE) and/or multipath (DM or NVMe): nvme0n1

  • Storage layout ("lsblk -ipo NAME,KNAME,PKNAME,TRAN,TYPE,FSTYPE,LABEL,SIZE,MOUNTPOINT"):

NAME        MAJ:MIN RM  SIZE RO TYPE MOUNTPOINTS
zram0       252:0    0  3.7G  0 disk [SWAP]
nvme0n1     259:0    0  100G  0 disk 
├─nvme0n1p1 259:1    0    1M  0 part 
├─nvme0n1p2 259:2    0 1000M  0 part /boot
├─nvme0n1p3 259:3    0  100M  0 part /boot/efi
├─nvme0n1p4 259:4    0    4M  0 part 
└─nvme0n1p5 259:5    0 98.9G  0 part /home
                                     /

pcahyna commented at 2024-09-06 15:58:

@gdha if the Fedora test VMs switched to UEFI, there is no way to make the tests work in them. I need to find a way to switch the VMs to BIOS booting instead.

lzaoral commented at 2024-09-06 17:38:

@pcahyna It is possible to schedule TF tests both for BIOS and UEFI? It shouldn't be that hard to extend the current tests and rear combined with EFI isn't that uncommon set-up. GRUB2 is able to mount ISO images and chainload EFI executables (hopefully, that is enough to simulate real EFI environment): https://wiki.gentoo.org/wiki/GRUB/Chainloading#Dual-booting_Windows_on_UEFI_with_GPT What do you think about this idea?

pcahyna commented at 2024-09-06 18:20:

@lzaoral

It is possible to schedule TF tests both for BIOS and UEFI?

I am trying to do BIOS in #3314 , so far no luck. I suppose one can find a way to test with UEFI, but this would require some new test development and I would like to fix the current test runs first.

pcahyna commented at 2024-09-09 18:03:

As there is apparently no way currently to tell the infrastructure to give the test the environment that it needs, I am going to disable the problematic test (#3317) . I also plan to merge the change in configuration that requests BIOS ( https://github.com/rear/rear/pull/3314 ). It does not do anything yet, but it will make the tests ready when Testing Farm is enhanced to support that, plus it does not hurt to be more explicit about what the tests need.

[Export of Github issue for rear/rear.]