-
Bug
-
Resolution: Not a Bug
-
Normal
-
None
-
4.18
-
None
-
False
-
-
None
-
None
-
None
-
None
-
None
-
None
-
Metal Platform 283, Metal Platform 284, Metal Platform 285
-
3
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
When deploying OCP (using ABI) into diskless Dell PowerEdge R660 servers with FC SAN storage attached, FC.Slot (LUN) does not appear first in the boot order in BIOS (after first reboot, i.e. after RHCOS written to boot LUN), keeping virtualmedia (attached Agent ISO) first in the list, resulting in a booting loop (from ISO). Version of iDRAC is v7.20.60.50, slightly newer than tested in Red Hat.
Internal Slack conversations regarding this topic:
1. https://redhat-internal.slack.com/archives/CFP6ST0A3/p1769027361760519
2. https://redhat-internal.slack.com/archives/C02SPBZ4GPR/p1767961120027469
3. https://redhat-internal.slack.com/archives/C02SPBZ4GPR/p1769017747730529
4. https://redhat-internal.slack.com/archives/CFP6ST0A3/p1768210189969409
Version-Release number of selected component (if applicable):
OCP4.18, Dell R660, iDRAC v7.20.60.50
How reproducible:
always
Steps to Reproduce:
1. Attach ISO
2. Trigger installation
3. Wait for first server reboot - check BIOS or simply observe boot loop
Actual results:
booting from ISO again
Expected results:
booting from LUN
Additional info:
