coordination #53249
Updated by SLindoMansilla over 4 years ago
## Description Sometimes it happens that the system is not yet shutdown and rebooting from the previous module when entering grub_test. This has been seen after trying to workaround the missed tiano core screen on aarch64: https://openqa.opensuse.org/tests/940347#step/grub_test/1 We need to ensure that the booting is in progress as soon as we enter grub_test ## Acceptance criteria - **AC1:** The tasks 1, 1 and 2 and 3 are done before changing the code. - **AC2:** This ticket is refined again after tasks 1, 1 and 2 and 3 are done. - **AC3:** The problem is fixed. ## Tasks 1. <del>Find in which tests scenarios, the following modules are NOT schedule: reboot_after_installation, first_boots</del> 2. <del>In which scenarios grub_test is schedule, and what is the previous module that was executed?</del> 3. Find all modules executed after installation, reboot, boot - Migrate the data in the picture to confluence (do NOT upload the picture) *. *Unify all the scenarios to use wait_boot* not to be done yet