Skip to content

Commit 60f12fa

Browse files
authored
Merge pull request #47205 from tshwartz/BZ-1960690
BZ1960690 - Booting the image with virtual media doesn't work
2 parents c8606f3 + 934fe8c commit 60f12fa

File tree

1 file changed

+7
-2
lines changed

1 file changed

+7
-2
lines changed

modules/ipi-install-node-requirements.adoc

Lines changed: 7 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@
33
// * installing/installing_bare_metal_ipi/ipi-install-prerequisites.adoc
44

55
:_content-type: CONCEPT
6-
[id="node-requirements_{context}"'"]
6+
[id="node-requirements_{context}"]
77
= Node requirements
88

99
Installer-provisioned installation involves a number of hardware node requirements:
@@ -36,7 +36,12 @@ Do not deploy a cluster with only one worker node, because the cluster will depl
3636
3737
* *Network interfaces:* Each node must have at least one network interface for the routable `baremetal` network. Each node must have one network interface for a `provisioning` network when using the `provisioning` network for deployment. Using the `provisioning` network is the default configuration.
3838
39-
* *Unified extensible firmware interface (UEFI):* Installer-provisioned installation requires UEFI boot on all {product-title} nodes when using IPv6 addressing on the `provisioning` network. In addition, UEFI Device PXE Settings must be set to use the IPv6 protocol on the `provisioning` network NIC, but omitting the `provisioning` network removes this requirement.
39+
* *Unified Extensible Firmware Interface (UEFI):* Installer-provisioned installation requires UEFI boot on all {product-title} nodes when using IPv6 addressing on the `provisioning` network. In addition, UEFI Device PXE Settings must be set to use the IPv6 protocol on the `provisioning` network NIC, but omitting the `provisioning` network removes this requirement.
40+
+
41+
[IMPORTANT]
42+
====
43+
When starting the installation from virtual media such as an ISO image, delete all old UEFI boot table entries. If the boot table includes entries that are not generic entries provided by the firmware, the installation might fail.
44+
====
4045
4146
* *Secure Boot:* Many production scenarios require nodes with Secure Boot enabled to verify the node only boots with trusted software, such as UEFI firmware drivers, EFI applications, and the operating system. You may deploy with Secure Boot manually or managed.
4247
+

0 commit comments

Comments
 (0)