action #123984
closed
[boot][pxe][sut] Machine fozzie can not boot from pxe
Added by waynechen55 over 1 year ago.
Updated over 1 year ago.
Description
Observation¶
Machine fozzie can not boot from pxe. Please refer to the following screenshot:
The bios boot order looks correct:
Steps to reproduce¶
- ipmitool -I lanplus -C 3 -H fozzie-sp.qa.suse.de -U xxx -P xxx sol activate
- Wait for pxe boot menu
Impact¶
boot_from_pxe test module will fail
Problem¶
Looks like incorrect networking settings. SSH to fozzie also fails (either fozzie/fozzie-1.qa.suse.de or assigned ip address 172.16.222.112)
Suggestion¶
- Check whether it is properly configured in the right network
Workaround¶
May need to disable associated worker as well
Files
- Private changed from No to Yes
- Status changed from New to Resolved
- Assignee set to okurz
- Target version set to Ready
- Private changed from Yes to No
https://gitlab.suse.de/openqa/salt-pillars-openqa/-/merge_requests/487 was merged. The machine was not yet in the right VLAN. The machine should have been disabled in salt pillars already as long as that is not fully setup yet, sorry about that. What I did:
In https://racktables.nue.suse.com/index.php?page=object&tab=default&object_id=10126 check the port connection on the switch, found out it's ge32 on qanet15. Checked on http://qanet15nue.qa.suse.de and found the machine is in the VLAN 571 because the port was used for some ppc machine in before and 571 is ppc mgmt. I set the VLAN to 12 and logged into the machine over IPMI SoL and found in the process table that the machine runs NetworkManager. To get a new IP-adress and ensure the system ends up in the correct IP range I did
nmcli con down eth0; nmcli con up eth0; ip a
which gives
inet 10.162.2.99/18
so all good.
So that resolves this ticket albeit complete verification should be done in #123028
Also available in: Atom
PDF