Ironic loses access to the BMC when iLO shared port is used
Bug #1660609 reported by
Dmitry Tantsur
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| proliantutils |
New
|
Undecided
|
Unassigned | ||
Bug Description
I don't know if it's possible to fix, but I'd like some help with the issue initially reported as https:/
TL;DR they're using an iLO shared port, and while introspection somehow works (with a lot of errors in logs), deployment fails at some point, because the iLO driver cannot reach out to the BMC.
Is it something that is supposed to work? Do we maybe need to special case it in proliantutils and e.g. increase timeouts?
Revision history for this message
| Shivanand Tendulker (stendulker) wrote | #1 |
Revision history for this message
| Nisha Agarwal (agarwalnisha1980) wrote | #2 |
To post a comment you must log in.
Are there any ironic logs that could be shared for this issue.
The shared network port should not have any impact on Ironic functioning as long as the DHCP server and the bare metal are in the same subnet so that BOOTP requests could be served by the DHCP server. However the communication with the iLO for performing the power operation on the baremetal should not get impacted.
The parent bug suggests that inspection goes through, is it using Ironic-inspector or OOB inspection provided by iLO drivers? Can you also share the hardware and firmware details of the impacted Proliant system.