Skip to content

Commit 3ee0f07

Browse files
committed
HCIDOCS-371: 4.16 RN known issue
Signed-off-by: Avital Pinnick <[email protected]>
1 parent 00a5966 commit 3ee0f07

File tree

1 file changed

+3
-0
lines changed

1 file changed

+3
-0
lines changed

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

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -3058,6 +3058,9 @@ In the following tables, features are marked with the following statuses:
30583058
// HCIDOCS-365 - This issue should be fixed soon, in a 4.16.z release
30593059
* Do not update firmware for the `BareMetalHosts` (BMH) resource by editing the `HostFirmwareComponents` resource. Otherwise, the BMH remains in the `Preparing` state and executes the firmware update repeatedly. There is no workaround. (link:https://issues.redhat.com/browse/OCPBUGS-35559[*OCPBUGS-35559*])
30603060

3061+
// HCIDOCS-371
3062+
* Deploying an installer-provisioned cluster on bare metal fails when a proxy is used. A service in the bootstrap virtual machine cannot access IP address `0.0.0.0` through the proxy because of a regression bug. As a workaround, add `0.0.0.0` to the `noProxy` list. See xref:../installing/installing_bare_metal_ipi/ipi-install-installation-workflow.adoc#ipi-install-setting-proxy-settings-within-install-config_ipi-install-installation-workflow[Setting proxy settings] for details. (link:https://issues.redhat.com/browse/OCPBUGS-35818[*OCPBUGS-35818*])
3063+
30613064
* When installing a cluster on {aws-first} in a VPC that contains multiple CIDR blocks, if the machine network is configured to use a non-default CIDR block in the `install-config.yaml` file, the installation fails. (link:https://issues.redhat.com/browse/OCPBUGS-35054[*OCPBUGS-35054*])
30623065

30633066
* When a {product-title} {product-version} cluster is installed or configured as a postinstallation activity on a single VIOS host with virtual SCSI storage on {ibm-power-name} with multipath configured, the CoreOS nodes with multipath enabled fail to boot. This behavior is expected as only one path is available to the node. (link:https://issues.redhat.com/browse/OCPBUGS-32290[*OCPBUGS-32290*]).

0 commit comments

Comments
 (0)