QA (public) » openQA Project (public) » openQA Infrastructure (public)

Hi @xlai , is there a USB stick on this machine? Or do you know any change has been made to this machine recently? they used to run tests well but begun to fail to boot now.

CC @xguo as you are quite familiar with the two machines.

Julie_CAO wrote in #note-5:

Hi @xlai , is there a USB stick on this machine? Or do you know any change has been made to this machine recently? they used to run tests well but begun to fail to boot now.

No, the usbs are on bare-metal{1,2}. And I do not see changes on the two machines from what I know.

dheidler wrote in #note-6:

• Took bare-metal5 out of production
• PXE or bios bootdev selection via ipmitool for next boot are NOT followed (at least using chassis bootdev pxe chassis power off chassis power on despite chassis bootparam get 5 showing otherwise)
• disabled quiet boot via bios setup
• still no change
• deleted sles boot entry and put network boot to first in order
• reenabled
• let's see https://openqa.suse.de/tests/16203423#live

Thanks for these actions, but it still failed to boot in https://openqa.suse.de/tests/16203423

redfishtool -r bare-metal5-ipmi.qe.prg2.suse.org -u ***** -p ***** Systems get | jq .Boot
{
  "BootSourceOverrideEnabled": "Once",
  "BootSourceOverrideMode": "UEFI",
  "BootSourceOverrideTarget": "Pxe",
  "BootSourceOverrideTarget@Redfish.AllowableValues": [
    "None",
    "Pxe",
    "Floppy",
    "Cd",
    "Usb",
    "Hdd",
    "BiosSetup",
    "UsbCd",
    "UefiBootNext",
    "UefiHttp"
  ],
  "BootOptions": {
    "@odata.id": "/redfish/v1/Systems/1/BootOptions"
  },
  "BootNext": null,
  "BootOrder": [
    "Boot0000",
    "Boot0003",
    "Boot0004",
    "Boot0002"
  ]
}

Redshift shows similar output as IPMITOOL does.

Updated BIOS from 2.3a to 2.4 and BMC from 01.02.09 to 01.03.05 on bare-metal5

@xguo Do you have ideas?

@xlai shall we pull them out of the OSD worker pool until the ticket is resolved?

Has it been tried if selecting pxe boot from bios works? Besides, I may suggest to check boot options in bios, allowing only pxe boot and disk boot.

@xlai shall we pull them out of the OSD worker pool until the ticket is resolved?

Yes, please help to.

Some machines really don't want to have ipmi controlled boot devices.

With kernel baremetal hardware, we solved this with a workaround. We have set those of our machines to always boot from PXE first and their first NVMe as second boot device. They always boot, get their bootscript fron the baremetal support service. When we don't want to install them, we just use https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/7c85092bafb2a6ca9f64d91b871544790da683ce/tests/installation/ipxe_install.pm#L126 and the machine boots from disk. I've mostly observed this for UEFI machines and don't remember to encounter it for legacy boot.

Not sure if this helps you.

Julie_CAO wrote in #note-13:

@xguo Do you have ideas?

No ideas.

Try to add IPMI_BACKEND_MC_RESET=1. but, confirm that does not work very well with bare-metal5 either. bare-metal5 is still unstable now.

FYI.
Refer to https://openqa.suse.de/admin/workers/3992 for more details.