QA (public) » openQA Project (public) » openQA Tests (public) » qe-yam

As a Quality Engineer I would like to automate yast2 bootloader with REST API
and validate properly setting written in the system with this module.

Let's start with in 'Boot Code Options' as follows:

1. Open yast2 bootloader and validate in the UI that the default options from installation which we are going to manipulate are properly processed by the module and has correct initial values.
   • Boot Loader: GRUB2
   • Write to Partition: no
   • Write to Master Boot Record: yes
   • Set active Flag in Partition: yes
   • Write generic Boot Code to MBR: no
2. Check with command line than GRUB is written in the MBR of the disk:
   • Validate file: /etc/default/grub_installdevice (YaST use it to control most of the settings)
   • Run: dd if=/dev/vda bs=512 count=1 | hexdump -C | grep GRUB
3. Open yast2 bootloader and check 'Write generic Boot Code to MBR' and apply changes.
4. From console check that GRUB is still in the MBR because it has priority over generic code.
5. Open yast2 bootloader and unselect 'Write to MBR' and apply changes.

6. Check that GRUB is not there anymore and generic boot from syslinux is written.
   Output of the following commands should be the same:

   dd if=/dev/vda bs=440 count=1 | hexdump -C
   cat /usr/share/syslinux/gptmbr.bin | hexdump -C
   

7. Optionally we could do some extra actions with UI:

   • Get a warning if we try to switch to GRUB2 for EFI.
   • Click on Edit Disk Boot Order and delete all disks, click on delete on empty list if possible (see bsc#1183218).

8. On the console check the map between BIOS drives and OS devices in /boot/grub2/device.map is correct for your hard disk(s).
   Additionally we could check a BIOS limitation by adding fake disks until you have a list greater than 8 disks.

9. Open yast2 bootloader again, go to Edit Disk Boot Order and verify that all the fake line where interpreted by the module as disks,
   then apply changes and a warning should be displayed preventing to add more than 8 devices instead of an Internal error (see bsc#1183218).