From 647febb97b43eaf0dbc035808b0158768d5be1b0 Mon Sep 17 00:00:00 2001 From: Ashley Hardin Date: Wed, 14 Oct 2020 17:35:43 -0400 Subject: [PATCH] Added critical known issues to 4.6 release notes --- release_notes/ocp-4-6-release-notes.adoc | 15 ++++++++++++--- 1 file changed, 12 insertions(+), 3 deletions(-) diff --git a/release_notes/ocp-4-6-release-notes.adoc b/release_notes/ocp-4-6-release-notes.adoc index 17524ce50c..694e6e23bb 100644 --- a/release_notes/ocp-4-6-release-notes.adoc +++ b/release_notes/ocp-4-6-release-notes.adoc @@ -1329,6 +1329,18 @@ Note the following restrictions for {product-title} on IBM Power: [id="ocp-4-6-known-issues"] == Known issues +* Currently, upgrading from {product-title} 4.5 to {product-version} with the OVN-Kubernetes pod network provider will not work. This will be resolved in a future 4.6.z release. (link:https://bugzilla.redhat.com/show_bug.cgi?id=1880591[*BZ#1880591*]) + +* Currently, scaling up {op-system-base-full} worker nodes on a cluster with the OVN-Kubernetes pod network provider will not work. This will be resolved in a future {op-system-base} 7.8.z and {op-system-base} 7.9.z release. +(link:https://bugzilla.redhat.com/show_bug.cgi?id=1884323[*BZ#1884323*], link:https://bugzilla.redhat.com/show_bug.cgi?id=1871935[*BZ#1871935*]) + +* Downgrading from {product-title} {product-version} to 4.5 will be fixed in a future 4.5.z release. +(link:https://bugzilla.redhat.com/show_bug.cgi?id=1882394[*BZ#1882394*], link:https://bugzilla.redhat.com/show_bug.cgi?id=1886148[*BZ#1886148*], link:https://bugzilla.redhat.com/show_bug.cgi?id=1886127[*BZ#1886127*]) + +* Currently, upgrading from {product-title} 4.5 to {product-version} with {op-system-base-full} worker nodes does not work. This will be resolved in a future 4.6.z release. First, upgrade {op-system-base}, then upgrade the cluster, and then run the normal {op-system-base} upgrade playbook again. (link:https://bugzilla.redhat.com/show_bug.cgi?id=1887607[*BZ#1887607*]) + +* {product-title} 4.5 to {product-version} upgrade fails when an external network is configured on a bond device; the `ovs-configuration` service fails and nodes becomes unreachable. (link:https://bugzilla.redhat.com/show_bug.cgi?id=1887545[*BZ#1887545*]) + // TODO: This known issue should carry forward to 4.7 and beyond! * In {product-title} 4.1, anonymous users could access discovery endpoints. Later releases revoked this access to reduce the possible attack surface for security exploits because some discovery endpoints are forwarded to aggregated API servers. However, unauthenticated access is preserved in upgraded clusters so that existing use cases are not broken. + @@ -1402,9 +1414,6 @@ down. * Private, disconnected cluster installations are not supported for AWS GovCloud when installing in the `us-gov-east-1` region due to a known issue. (link:https://bugzilla.redhat.com/show_bug.cgi?id=1881262[*BZ#1881262*]). -* Installing {product-title} version 4.6 on {rh-virtualization-first} requires {rh-virtualization} version 4.4. If you are running an earlier version of {product-title} on {rh-virtualization} 4.3, do not update it to {product-title} version 4.6. Red Hat has not tested running {product-title} version 4.6 on {rh-virtualization} version 4.3 and does not support this combination. For more information, see link:https://access.redhat.com/articles/4763741[{product-title} 4.x Tested Integrations (for x86_x64)]. -(link:https://bugzilla.redhat.com/show_bug.cgi?id=1862586[*BZ#1862586*]) - * Firewall rules used by machines not prefixed with the infrastructure ID are preserved when destroying a cluster running on Google Cloud Platform (GCP) with installer-provisioned infrastructure. This causes the destroy process of the installation program to fail. As a workaround, you must manually delete the firewall rule of the machine in the GCP web console: + [source,terminal]