ipmitool crashes when incorrect tftp address is entered in petiboot
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ipmitool |
Invalid
|
Undecided
|
Ubuntu on IBM Power Systems Bug Triage | ||
The Ubuntu-power-systems project |
Invalid
|
High
|
David Britton |
Bug Description
Problem Description:
While navigating petiboot on the Power9, configure a specific interface with a static IP, set the gateway and dns appropiately. The enter the TFTP URL.
I mistakenly fat fingered the TFTP URL and confirmed my selection. The host attempts to PXE boot with the correct static ip address settings, however it attempts to access an invalid TFTP URL.
Once this occurs.
[eth0] Failed to download tftp://
Then IPMI Will exit.
SIGN INT: Close Interface IPMI v2.0 RMCP+ LAN Interface
Any attempt to reconnect to the the host via ipmitool fails.
Workaround:
The host must be cold power cycled, until the BMC resets itself. Then ipmitool will reconnect to the host.
Changed in ipmitool: | |
assignee: | nobody → Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) |
Changed in ubuntu-power-systems: | |
importance: | Undecided → High |
assignee: | nobody → Canonical Server Team (canonical-server) |
tags: | added: architecture-ppc64le |
Changed in ubuntu-power-systems: | |
assignee: | Canonical Server Team (canonical-server) → David Britton (davidpbritton) |
tags: | added: triage-r |
Changed in ubuntu-power-systems: | |
status: | Incomplete → Invalid |
What is the "crash" in ipmitool? Receiving a SIGINT is not a crash (afaict), it's the BMC saying to ipmitool to close the connection.
If the BMC is so fragile that it has to be cold power cycled to reset on bad input, that's a bug in the BMC firmware, not ipmitool.