Project

General

Profile

Actions
Copy link

action #173344

closed

coordination #161414: [epic] Improved salt based infrastructure management

Extend iPXE in qe/oqa.*.suse.org to also display on local console size:S

Added by okurz 2 months ago. Updated 17 days ago.

Status:
Resolved
Priority:
Normal
Assignee:
gpathak
Category:
Feature requests
Target version:
openQA Project (public) - Ready
Start date:
Due date:
% Done:

0%

Estimated time:
Tags:
infra, nue2

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

Files

Download all files
clipboard-202501091746-zolpt.png (207 KB) clipboard-202501091746-zolpt.png gpathak, 2025-01-09 12:16
ipxe-boot.mp4 (253 KB) ipxe-boot.mp4 gpathak, 2025-01-12 12:38
ipxe-boot.mp4 (4.48 MB) ipxe-boot.mp4 gpathak, 2025-01-12 16:46

Related issues 1 (0 open — 1 closed)

Copied from openQA Infrastructure (public) - action #170077: Put more storage into qamaster "to make our lives easier in general" size:MResolvedokurz2024-11-19

Actions
Actions
Copy link
 #1

Updated by okurz 2 months ago

  • Copied from action #170077: Put more storage into qamaster "to make our lives easier in general" size:M added
Actions
Copy link
 #2

Updated by okurz about 2 months ago

  • Target version changed from future to Ready
Actions
Copy link
 #3

Updated by okurz about 1 month ago

  • Description updated (diff)
  • Status changed from New to Workable
Actions
Copy link
 #4

Updated by livdywan about 1 month ago

  • Subject changed from Extend iPXE in qe/oqa.*.suse.org to also display on local console to Extend iPXE in qe/oqa.*.suse.org to also display on local console size:S
Actions
Copy link
 #5

Updated by gpathak about 1 month ago

  • Status changed from Workable to In Progress
  • Assignee set to gpathak
Actions
Copy link
 #7

Updated by openqa_review about 1 month ago

  • Due date set to 2025-01-11

Setting due date based on mean cycle time of SUSE QE Tools

Actions
Copy link
 #8

Updated by okurz 29 days ago

  • Status changed from In Progress to Workable
Actions
Copy link
 #9

Updated by gpathak 23 days ago

  • Status changed from Workable to In Progress
Actions
Copy link
 #10

Updated by gpathak 22 days 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.

Actions
Copy link
 #11

Updated by nicksinger 22 days 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 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.

https://github.com/os-autoinst/scripts/blob/master/ipxe/README.md contains some references to internal gitlab repos which deploy on these hosts.

Actions
Copy link
 #12

Updated by gpathak 22 days 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/

Actions
Copy link
 #13

Updated by nicksinger 22 days 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.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/

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?

Actions
Copy link
 #14

Updated by gpathak 22 days 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

Actions
Copy link
 #15

Updated by gpathak 22 days ago

Deployed on O3 as well:

Actions
Copy link
 #16

Updated by livdywan 21 days 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.

Actions
Copy link
 #17

Updated by gpathak 21 days 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

Actions
Copy link
 #18

Updated by okurz 21 days 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.

Actions
Copy link
 #19

Updated by gpathak 19 days ago

Trying locally using libvirt to boot via PXE is able to load the menu.ipxe file.

Actions
Copy link
 #20

Updated by okurz 19 days 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

Actions
Copy link
 #21

Updated by gpathak 19 days ago

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

Actions
Copy link
 #22

Updated by okurz 19 days ago

Then everything necessary was done. You can resolve the ticket

Actions
Copy link
 #23

Updated by gpathak 18 days ago

  • Status changed from Workable to Resolved
Actions
Copy link
 #24

Updated by okurz 17 days ago

  • Due date deleted (2025-01-11)
Actions
Copy link

Also available in: Atom PDF