Skip to content

Commit

Permalink
OSDOCS-12973: Documented the 4.17.10 z-stream release notes
Browse files Browse the repository at this point in the history
  • Loading branch information
dfitzmau committed Dec 20, 2024
1 parent 7b50a53 commit 6587352
Showing 1 changed file with 39 additions and 0 deletions.
39 changes: 39 additions & 0 deletions release_notes/ocp-4-17-release-notes.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -2874,6 +2874,45 @@ This section will continue to be updated over time to provide notes on enhanceme
For any {product-title} release, always review the instructions on xref:../updating/updating_a_cluster/updating-cluster-web-console.adoc#updating-cluster-web-console[updating your cluster] properly.
====

// 4.17.10
[id="ocp-4-17-10_{context}"]
=== RHBA-2024:11522 - {product-title} {product-version}.10 bug fix, and security update advisory

Issued: 02 January 2024

{product-title} release {product-version}.10 is now available. The list of bug fixes that are included in the update is documented in the link:https://access.redhat.com/errata/RHBA-2024:11522[RHBA-2024:11522] advisory. The RPM packages that are included in the update are provided by the link:https://access.redhat.com/errata/RHBA-2024:11525[RHBA-2024:11525] advisory.

Space precluded documenting all of the container images for this release in the advisory.

You can view the container images in this release by running the following command:

[source,terminal]
----
$ oc adm release info 4.17.10 --pullspecs
----

[id="ocp-4-17-10-bug-fixes_{context}"]
==== Bug fixes

// SME review
* Previously, when the webhook token authenticator was enabled and had the authorization type set to `None`, the {product-title} web console would consistently crash. With this release, a bug fix ensures that this configuration does not cause the {product-title} web console to crash. (link:https://issues.redhat.com/browse/OCPBUGS-46390[*OCPBUGS-46390*])

// SME review
* Previously, a hard eviction of a pod in a node caused a pod to enter a termination grace period instead of instantly shutting down and getting deleted by the kubelet. Each pod that enters a termination grace period exhausts the resources of the node. With this release, a bug fix ensures that a pod enter a `1` second termination grace period so that the kubelet can shut down and then delete the pod. (link:https://issues.redhat.com/browse/OCPBUGS-46390[*OCPBUGS-46390*])

// https://issues.redhat.com/browse/OCPBUGS-46082 marked as internal. Check closer to the release date if the Jira switched status.

// SME review
* Previously, the `SiteConfig` custom resource (CR) configuration, which configures ingress rules and sevices for a cluster, caused the `BareMetalHost` CR to remain in a deleted state instead of being deleted as part of the cluster cleanup operation. With this release, this issue no longer occurs provided that you update to the GitOps Operator to version 1.13 or a later version. (link:https://issues.redhat.com/browse/OCPBUGS-46071[*OCPBUGS-46071*])





[id="ocp-4-17-10-updating_{context}"]
==== Updating
To update an {product-title} 4.17 cluster to this latest release, see xref:../updating/updating_a_cluster/updating-cluster-cli.adoc#updating-cluster-cli[Updating a cluster using the CLI].

// 4.17.9
[id="ocp-4-17-9_{context}"]
=== RHBA-2024:11010 - {product-title} {product-version}.9 bug fix, and security update advisory
Expand Down

0 comments on commit 6587352

Please sign in to comment.