action #179389
Updated by waynechen55 9 days ago
## Observation
I found ```scooter-1.qe.prg2.suse.org``` and ```bare-metal6.qe.prg2.suse.org``` can not boot from ipxe because ```no media present```. Actually media is present, for example:
```
#!ipxe
echo ++++++++++++++++++++++++++++++++++++++++++
echo ++++++++++++ openQA ipxe boot ++++++++++++
echo + Host: scooter-1.qe.prg2.suse.org
echo ++++++++++++++++++++++++++++++++++++++++++
kernel http://openqa.suse.de/assets/repo/SLE-15-SP7-Online-x86_64-Build77.5-Media1/boot/x86_64/loader/linux install=http://openqa.suse.de/assets/repo/SLE-15-SP7-Online-x86_64-Build77.5-Media1 regurl=http://all-77.5.proxy.scc.suse.de root=/dev/ram0 initrd=initrd textmode=1 autoyast=http://grenache-1.oqa.prg2.suse.org:20173/G4KA4ahXeT8bQPs_/files/scooter-1.qe.prg2.suse.orgvirt_autotest/host_unattended_installation_files/autoyast/dev_host_15.xml sshd=1 sshpassword=xxxxxxxxxx plymouth.enable=0 video=1024x768 vt.color=0x07 console=ttyS1,115200 Y2DEBUG=1 linuxrc.log=/dev/ttyS1 linuxrc.core=/dev/ttyS1 linuxrc.debug=4,trace reboot_timeout=0
initrd http://openqa.suse.de/assets/repo/SLE-15-SP7-Online-x86_64-Build77.5-Media1/boot/x86_64/loader/initrd
boot200 OK
```
The boot process reports:
```
>>No Media Present......^[[22;1H^[[0;37;40m^[[22;1H ^[[22;1H^[[22;1HREADY TO BOOT...^[[22;1H^[[22;1H ^[[22;1H^[[22;1HREADY TO BOOT...^[[1;37;40m^[[2J^[[1;1H^[[1;1H^M
>>Checking Media Presence......^M
>>No Media Present......^[[22;1H^[[0;37;40m^[[22;1H ^[[22;1H^[[22;1HREADY TO BOOT...^[[0;30;40m^[[2J^[[1;1H^[[0;37;40mPlease press 't' to show the boot menu on this console
```
openQA jobs:
https://openqa.suse.de/tests/17133130#step/ipxe_install/3
https://openqa.suse.de/tests/17133125#step/ipxe_install/3
https://openqa.suse.de/tests/17133108#step/ipxe_install/3
https://openqa.suse.de/tests/17133109#step/ipxe_install/1
## Steps to reproduce
* set ipxe boot script for scooter-1 and bare-metal6
* boot from ipxe
## Impact
ipmi backedn tests can not run with these two machines
## Problem
Looks like connection is broken ???
## Suggestions
* Recent network changes
* Recent worker changes
## Workaround
n/a