action #45161
closed[sle][functional][y][ipmi] isolate pxe part and installer boot from boot_from_pxe
0%
Description
In order to run post_fail_hook and benefit from information about potential installer boot issues, I would like to suggest split boot_from_pxe.
With respect to PXE limitations and its purpose to specify kernel boot parameters, I would expect to have a better chance to distinguish between a production bug and possible test environmental issues.
The post_fail_hook call is currently bond to the TTYs/consoles, which are not available during the interaction with PXE. TTYs/consoles are available just before yast2 installer shows up. https://openqa.suse.de/tests/2540029#step/boot_from_pxe/7.
There are no benefits from post fail hook execution as long as the failure happens in PXE.
Updated by SLindoMansilla over 5 years ago
- Category set to Enhancement to existing tests
Updated by riafarov almost 5 years ago
- Due date set to 2019-05-21
- Target version changed from Milestone 24 to Milestone 25
Updated by JERiveraMoya almost 5 years ago
- Status changed from New to Workable
- Estimated time set to 3.00 h
Updated by mloviska almost 5 years ago
There is a mystery code which we do not use at all, although it might be used by our Beijing colleagues.
Needle orthos-grub-boot-linux does not exist in our repos and it was never matched by OSD.
Updated by mloviska almost 5 years ago
- Status changed from Workable to Feedback
Updated by JERiveraMoya almost 5 years ago
- Due date changed from 2019-05-21 to 2019-06-04
Waiting for further comments in PR. We could check Virtualization group due to that team has some quite a lot ipmi jobs that could be useful.
Updated by mloviska almost 5 years ago
- Status changed from Feedback to Rejected
Not bringing any benefit eventually. PR closed