action #173344
closedcoordination #161414: [epic] Improved salt based infrastructure management
Extend iPXE in qe/oqa.*.suse.org to also display on local console size:S
0%
Description
Motivation¶
While working on qamaster okurz realized that the iPXE boot menu includes boot parameters like console=ttyS1 to show content on a serial terminal which is also accessible over IPMI SoL but then a locally connected display as well as KVMViewer display does not show useful console content. iPXE should also display on local console, e.g. add console=tty0 console=ttyS1 to display also something on local screen, not just remotely
Acceptance criteria¶
- AC1: qamaster and other machines show kernel boot logs + a login prompt on both local console as well as IPMI SoL
Suggestions¶
- Compare to boot parameters we set for machines in salt, e.g. https://gitlab.suse.de/openqa/salt-states-openqa/-/blob/master/openqa/worker.sls#L10
- Extend iPXE configuration in the according code, possibly https://github.com/os-autoinst/scripts/tree/master/ipxe, e.g. see https://github.com/os-autoinst/scripts/blob/master/ipxe/menu.ipxe#L44
- https://github.com/os-autoinst/scripts/blob/master/ipxe/menu.ipxe#L56 is already using
console=tty. Just put that everywhere else - Ensure the solution is deployed to our iPXE hosts which are probably multiple by now, e.g. qa-jump.qe.nue2.suse.org and netboot.qe.prg2.suse.org
- Semi-related: https://gitlab.suse.de/openqa/salt-states-openqa/-/merge_requests/1037
Files
| clipboard-202501091746-zolpt.png (207 KB) clipboard-202501091746-zolpt.png | |||
| ipxe-boot.mp4 (253 KB) ipxe-boot.mp4 | |||
| ipxe-boot.mp4 (4.48 MB) ipxe-boot.mp4 |
Updated by okurz 3 months ago
- Copied from action #170077: Put more storage into qamaster "to make our lives easier in general" size:M added
Updated by gpathak 2 months ago
Pull Request Created: https://github.com/os-autoinst/scripts/pull/361
Updated by openqa_review 2 months ago
- Due date set to 2025-01-11
Setting due date based on mean cycle time of SUSE QE Tools
Updated by gpathak about 2 months ago
- Status changed from Workable to In Progress
Updated by gpathak about 2 months ago
@okurz @nicksinger
How can I trigger the deployment https://github.com/os-autoinst/scripts/pull/361 only on ipxe hosts?
I can see netboot.qe.prg2.suse.org: in https://gitlab.suse.de/openqa/osd-deployment/-/jobs/3631478 but I cannot find qa-jump.qe.nue2.suse.org.
Updated by nicksinger about 2 months ago
gpathak wrote in #note-10:
@okurz @nicksinger
How can I trigger the deployment https://github.com/os-autoinst/scripts/pull/361 only on ipxe hosts?
I can seenetboot.qe.prg2.suse.org:in https://gitlab.suse.de/openqa/osd-deployment/-/jobs/3631478 but I cannot findqa-jump.qe.nue2.suse.org.
https://github.com/os-autoinst/scripts/blob/master/ipxe/README.md contains some references to internal gitlab repos which deploy on these hosts.
Updated by gpathak about 2 months ago
Thanks @nicksinger!
The changes are deployed in the git repo checkout folder /srv/tftpboot/ipxe/os-autoinst-scripts/ipxe/menu.ipxe file on both the hosts qa-jump.qe.nue2.suse.org as well as netboot.qe.prg2.suse.org.
But still, it is not yet reflecting at the top webpage on netboot host: http://netboot.qe.prg2.suse.org/ipxe/
Updated by nicksinger about 2 months ago
gpathak wrote in #note-12:
Thanks @nicksinger!
The changes are deployed in the git repo checkout folder
/srv/tftpboot/ipxe/os-autoinst-scripts/ipxe/menu.ipxefile on both the hostsqa-jump.qe.nue2.suse.orgas well asnetboot.qe.prg2.suse.org.But still, it is not yet reflecting at the top webpage on netboot host: http://netboot.qe.prg2.suse.org/ipxe/
I clicked "restart" on https://gitlab.suse.de/qa-sle/netboot-configs/-/jobs/3627432 and got https://gitlab.suse.de/qa-sle/netboot-configs/-/jobs/3632585 which shows:
From https://github.com/os-autoinst/scripts
f8b2279..40ea78a master -> origin/master
Updating f8b2279..40ea78a
also http://netboot.qe.prg2.suse.org/ipxe/readme.txt is now present so it should be fine now or anything missing still? Did you check if OSD itself is also updated?
Updated by gpathak about 2 months ago
nicksinger wrote in #note-13:
also http://netboot.qe.prg2.suse.org/ipxe/readme.txt is now present so it should be fine now or anything missing still? Did you check if OSD itself is also updated?
I think it is O3, https://github.com/os-autoinst/scripts/tree/master/ipxe
Updated by livdywan about 2 months ago
- Status changed from In Progress to Feedback
Please provide a job that shows that at the least booting still works (reboot any affected machine if your choosing if that did not already happen). Then I'd say this can be resolved.
Updated by gpathak about 2 months ago
I cannot find a worker that has executed an ipxe install test pointing the URL to either netboot.qe.prg2.suse.org or qa-jump.qe.nue2.suse.org for ipxe boot
Updated by okurz about 2 months ago
- Status changed from Feedback to Workable
this is not about openQA or openQA jobs. You can basically pick any machine in the according network, reboot it over network and see if it shows the expected kernel logs on bootup over serial line.
Updated by gpathak about 2 months ago
- File ipxe-boot.mp4 ipxe-boot.mp4 added
Trying locally using libvirt to boot via PXE is able to load the menu.ipxe file.
Updated by okurz about 2 months ago
Good. Also in your VM you should be able to test that booting an entry from ipxe shows output both on tty1 as well as the serial port
Updated by gpathak about 2 months ago
- File ipxe-boot.mp4 ipxe-boot.mp4 added
okurz wrote in #note-20:
Good. Also in your VM you should be able to test that booting an entry from ipxe shows output both on tty1 as well as the serial port
The default console on Kernel command line is set to ttyS1 but the serial console on my VM is ttyS0, unfortunately editing kernel cmdline wasn't working on my VM, but on tty console I was able to view the boot logs
Updated by okurz about 2 months ago
Then everything necessary was done. You can resolve the ticket