Skip to content

Commit 7524417

Browse files
authored
Merge pull request #77822 from johnwilkins/HCIDOCS-72-rn
HCIDOCS-72: Added a release note
2 parents 0b5736d + 9aeccdd commit 7524417

File tree

1 file changed

+6
-0
lines changed

1 file changed

+6
-0
lines changed

release_notes/ocp-4-16-release-notes.adoc

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1112,6 +1112,12 @@ For more information, see xref:../support/gathering-cluster-data.adoc#about-must
11121112

11131113
In {product-title} {product-version} and later, you can edit the baseboard management controller (BMC) address in the `BareMetalHost` resource of a bare-metal node. The node must be in the `Provisioned`, `ExternallyProvisioned`, `Registering`, or `Available` state. Editing the BMC address in the `BareMetalHost` resource will not result in deprovisioning the node. See xref:../post_installation_configuration/bare-metal-configuration.adoc#editing-a-baremetalhost-resource_post-install-bare-metal-configuration[Editing a BareMetalHost resource] for additional details.
11141114

1115+
[id="ocp-4-16-attaching-a-non-bootable-iso_{context}"]
1116+
==== Attaching a non-bootable ISO
1117+
1118+
In {product-title} {product-version} and later, you can attach a generic, non-bootable ISO virtual media image to a provisioned node by using the `DataImage` resource. After you apply the resource, the ISO image becomes accessible to the operating system on the next reboot.
1119+
The node must use Redfish or drivers derived from it to support this feature. The node must be in the `Provisioned` or `ExternallyProvisioned` state. See xref:../post_installation_configuration/bare-metal-configuration.adoc#attaching-a-non-bootable-iso-to-a-bare-metal-node_post-install-bare-metal-configuration[Attaching a non-bootable ISO to a bare-metal node] for additional details.
1120+
11151121
[id="ocp-4-16-monitoring_{context}"]
11161122
=== Monitoring
11171123

0 commit comments

Comments
 (0)