OSDOCS#13971: Update the z-stream RNs for 4.17.24 #91900

tmalove · 2025-04-09T02:34:50Z

Version(s):
4.17

Issue:
OSDOCS-13971

Link to docs preview:
4.17.24

QE review:

QE has approved this change.
n/a for z-stream relnotes.

Additional information:
The errata URLs will return 404 until the go-live date of 4/9/25.

ocpdocs-previewbot · 2025-04-09T02:43:31Z

🤖 Wed Apr 09 22:23:35 - Prow CI generated the docs preview:

https://91900--ocpdocs-pr.netlify.app/openshift-enterprise/latest/release_notes/ocp-4-17-release-notes.html

tmalove · 2025-04-09T02:57:55Z

/label peer-review-needed

max-cx · 2025-04-09T09:30:47Z

/label peer-review-in-progress
/remove-label peer-review-needed

max-cx

🙂
Enjoyed reading your release notes.
Added some suggestions for you to consider.

max-cx · 2025-04-09T09:32:36Z

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

@@ -2879,6 +2879,39 @@ 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.24
+[id="ocp-4-17-24_{context}"]
+=== RHBA-2025:3565 - {product-title} {product-version}.24 bug fix, and security update advisory


I suggest double-checking this comma, which appears likely redundant to me:

Suggested change

=== RHBA-2025:3565 - {product-title} {product-version}.24 bug fix, and security update advisory

=== RHBA-2025:3565 - {product-title} {product-version}.24 bug fix and security update advisory

I verified changing all of the 4.17 z-stream bug text with the team lead...done. Thx!

max-cx · 2025-04-09T09:36:28Z

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

+[id="ocp-4-17-24-bug-fixes_{context}"]
+==== Bug fixes
+
+* Previously, an update to the {ibm-cloud-name} Cloud Internet Services (CIS) implementation impacted the upstream Terraform plugin. If you attempted to create an external-facing cluster on {ibm-cloud-name}, an error occurred. With this release, you can use the installation program to create an external cluster on {product-title} without the plugin issue. (link:https://issues.redhat.com/browse/OCPBUGS-54357[*OCPBUGS-54357*])


As a reader, I find it difficult to understand what this paragraph means by the installation program. It would be helpful to define it as such by using an appositive in one of the preceding sentences or mention the product name or clarify a software category in this sentence.

max-cx · 2025-04-09T09:42:14Z

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

+
+* Previously, an update to the {ibm-cloud-name} Cloud Internet Services (CIS) implementation impacted the upstream Terraform plugin. If you attempted to create an external-facing cluster on {ibm-cloud-name}, an error occurred. With this release, you can use the installation program to create an external cluster on {product-title} without the plugin issue. (link:https://issues.redhat.com/browse/OCPBUGS-54357[*OCPBUGS-54357*])
+
+* Previously, when you built the agent ISO in a disconnected setup, an error occured. With this release, the setup completes without an error. (link:https://issues.redhat.com/browse/OCPBUGS-53378[*OCPBUGS-53378*])


I wonder if, despite all the guidance that we have been receiving about using you, we should be using you in some contexts such as this sentence. My concern is that if say most of the readers never built the agent ISO in a disconnected setup, they would be confused about being told that they previous experienced some problem that they don't remember ever experiencing.

Suggested change

* Previously, when you built the agent ISO in a disconnected setup, an error occured. With this release, the setup completes without an error. (link:https://issues.redhat.com/browse/OCPBUGS-53378[*OCPBUGS-53378*])

* Previously, when users tried building the agent ISO in a disconnected setup, an error occurred. With this release, the setup completes without an error. (link:https://issues.redhat.com/browse/OCPBUGS-53378[*OCPBUGS-53378*])

max-cx · 2025-04-09T09:48:24Z

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

+
+* Previously, when you built the agent ISO in a disconnected setup, an error occured. With this release, the setup completes without an error. (link:https://issues.redhat.com/browse/OCPBUGS-53378[*OCPBUGS-53378*])
+
+* Previously, the `ovn-ipsec-host` pod experienced a crash loop on RHEL worker nodes because of a missing shared library during the container execution. With this release, the `ovn-ipsec-host` pod successfully comes up on the worker node without an error. (link:https://issues.redhat.com/browse/OCPBUGS-52951[*OCPBUGS-52951*])


If a pod experienced a crash loop, this might or might not be an anthropomorphism, so this word choice might be worth a second thought unless you've already considered this. Also, international audiences might find it a bit difficult to follow what comes up means.

Suggested change

* Previously, the `ovn-ipsec-host` pod experienced a crash loop on RHEL worker nodes because of a missing shared library during the container execution. With this release, the `ovn-ipsec-host` pod successfully comes up on the worker node without an error. (link:https://issues.redhat.com/browse/OCPBUGS-52951[*OCPBUGS-52951*])

* Previously, the `ovn-ipsec-host` pod failed with a crash loop on RHEL worker nodes because of a missing shared library during the container execution. With this release, the `ovn-ipsec-host` pod successfully starts on the worker node without an error. (link:https://issues.redhat.com/browse/OCPBUGS-52951[*OCPBUGS-52951*])

max-cx · 2025-04-09T09:50:58Z

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

+
+* Previously, the `ovn-ipsec-host` pod experienced a crash loop on RHEL worker nodes because of a missing shared library during the container execution. With this release, the `ovn-ipsec-host` pod successfully comes up on the worker node without an error. (link:https://issues.redhat.com/browse/OCPBUGS-52951[*OCPBUGS-52951*])
+
+* Previously, the {olm-first} CSV annotation contained unexpected JSON, which was successfully parsed, but then resulted in a runtime error when attempting to use the resulting value. With this release, JSON values from OLM annotations are validated before use, errors are logged, and the console does not fail when an unexpected JSON is received in an annotation. (link:https://issues.redhat.com/browse/OCPBUGS-51277[(*OCPBUGS-51277*)])


It could be a little more readable if the JSON format were used in a noun phrase here, for example:

Suggested change

* Previously, the {olm-first} CSV annotation contained unexpected JSON, which was successfully parsed, but then resulted in a runtime error when attempting to use the resulting value. With this release, JSON values from OLM annotations are validated before use, errors are logged, and the console does not fail when an unexpected JSON is received in an annotation. (link:https://issues.redhat.com/browse/OCPBUGS-51277[(*OCPBUGS-51277*)])

* Previously, the {olm-first} CSV annotation contained unexpected JSON data, which was successfully parsed, but then resulted in a runtime error when attempting to use the resulting value. With this release, JSON values from OLM annotations are validated before use, errors are logged, and the console does not fail when an unexpected JSON is received in an annotation. (link:https://issues.redhat.com/browse/OCPBUGS-51277[(*OCPBUGS-51277*)])

max-cx · 2025-04-09T09:54:27Z

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

+
+[id="ocp-4-17-24-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].


A rewording such as this might help avoid confusion for some readers like me:

Suggested change

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].

To update a cluster from an earlier {product-title} version to this version, 4.17.24, see xref:../updating/updating_a_cluster/updating-cluster-cli.adoc#updating-cluster-cli[Updating a cluster using the CLI].

I'll have to run this past my team lead, because it involves a template change for all of the releases. If approved, I will change all of the 4.17 z-stream relnotes. Thank you!

max-cx · 2025-04-09T09:57:01Z

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

+[id="ocp-4-17-24_{context}"]
+=== RHBA-2025:3565 - {product-title} {product-version}.24 bug fix, and security update advisory
+
+Issued: 09 April 2025


Depending on whether it is possible or not, I'd recommend dropping the leading zero to make it more human-readable:

Suggested change

Issued: 09 April 2025

Issued: 9 April 2025

max-cx · 2025-04-09T10:18:25Z

/label peer-review-done
/remove-label peer-review-in-progress

tmalove · 2025-04-09T19:01:04Z

@max-cx Thanks for all of your input!

tmalove · 2025-04-09T19:56:33Z

/label merge-review-needed

mburke5678 · 2025-04-09T21:54:33Z

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

+=== RHBA-2025:3565 - {product-title} {product-version}.24 bug fix and security update advisory
+
+Issued: 9 April 2025
+
+{product-title} release {product-version}.24 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-2025:3565[RHBA-2025:3565] advisory. The RPM packages that are included in the update are provided by the link:https://access.redhat.com/errata/RHBA-2025:3567[RHBA-2025:3567] advisory.


Suggested change

=== RHBA-2025:3565 - {product-title} {product-version}.24 bug fix and security update advisory

Issued: 9 April 2025

{product-title} release {product-version}.24 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-2025:3565[RHBA-2025:3565] advisory. The RPM packages that are included in the update are provided by the link:https://access.redhat.com/errata/RHBA-2025:3567[RHBA-2025:3567] advisory.

=== RHSA-2025:3565 - {product-title} {product-version}.24 bug fix and security update advisory

Issued: 9 April 2025

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

openshift-ci · 2025-04-09T22:25:10Z

@tmalove: all tests passed!

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

openshift-ci bot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Apr 9, 2025

openshift-ci bot added the peer-review-needed Signifies that the peer review team needs to review this PR label Apr 9, 2025

openshift-ci bot added peer-review-in-progress Signifies that the peer review team is reviewing this PR and removed peer-review-needed Signifies that the peer review team needs to review this PR labels Apr 9, 2025

max-cx reviewed Apr 9, 2025

View reviewed changes

openshift-ci bot added peer-review-done Signifies that the peer review team has reviewed this PR and removed peer-review-in-progress Signifies that the peer review team is reviewing this PR labels Apr 9, 2025

tmalove force-pushed the OSDOCS-13971 branch 2 times, most recently from d3deca1 to 9fe66e7 Compare April 9, 2025 19:31

openshift-ci bot added the merge-review-needed Signifies that the merge review team needs to review this PR label Apr 9, 2025

mburke5678 added merge-review-in-progress Signifies that the merge review team is reviewing this PR and removed merge-review-in-progress Signifies that the merge review team is reviewing this PR merge-review-needed Signifies that the merge review team needs to review this PR labels Apr 9, 2025

mburke5678 reviewed Apr 9, 2025

View reviewed changes

OSDOCS-13971: 4.17.24 z-stream RN

d91a697

tmalove force-pushed the OSDOCS-13971 branch from 85e7cfd to d91a697 Compare April 9, 2025 22:13

mburke5678 merged commit 0dc4453 into openshift:enterprise-4.17 Apr 10, 2025
2 checks passed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

OSDOCS#13971: Update the z-stream RNs for 4.17.24 #91900

OSDOCS#13971: Update the z-stream RNs for 4.17.24 #91900

tmalove commented Apr 9, 2025 •

edited

Loading

ocpdocs-previewbot commented Apr 9, 2025 •

edited

Loading

tmalove commented Apr 9, 2025

max-cx commented Apr 9, 2025

max-cx left a comment •

edited

Loading

max-cx Apr 9, 2025

tmalove Apr 9, 2025

max-cx Apr 9, 2025

max-cx Apr 9, 2025

max-cx Apr 9, 2025

max-cx Apr 9, 2025

max-cx Apr 9, 2025

tmalove Apr 9, 2025

max-cx Apr 9, 2025 •

edited

Loading

max-cx commented Apr 9, 2025

tmalove commented Apr 9, 2025

tmalove commented Apr 9, 2025

mburke5678 Apr 9, 2025

openshift-ci bot commented Apr 9, 2025

	=== RHBA-2025:3565 - {product-title} {product-version}.24 bug fix, and security update advisory
	=== RHBA-2025:3565 - {product-title} {product-version}.24 bug fix and security update advisory


		* Previously, an update to the {ibm-cloud-name} Cloud Internet Services (CIS) implementation impacted the upstream Terraform plugin. If you attempted to create an external-facing cluster on {ibm-cloud-name}, an error occurred. With this release, you can use the installation program to create an external cluster on {product-title} without the plugin issue. (link:https://issues.redhat.com/browse/OCPBUGS-54357[OCPBUGS-54357])

		* Previously, when you built the agent ISO in a disconnected setup, an error occured. With this release, the setup completes without an error. (link:https://issues.redhat.com/browse/OCPBUGS-53378[OCPBUGS-53378])

	* Previously, when you built the agent ISO in a disconnected setup, an error occured. With this release, the setup completes without an error. (link:https://issues.redhat.com/browse/OCPBUGS-53378[OCPBUGS-53378])
	* Previously, when users tried building the agent ISO in a disconnected setup, an error occurred. With this release, the setup completes without an error. (link:https://issues.redhat.com/browse/OCPBUGS-53378[OCPBUGS-53378])


		* Previously, when you built the agent ISO in a disconnected setup, an error occured. With this release, the setup completes without an error. (link:https://issues.redhat.com/browse/OCPBUGS-53378[OCPBUGS-53378])

		* Previously, the `ovn-ipsec-host` pod experienced a crash loop on RHEL worker nodes because of a missing shared library during the container execution. With this release, the `ovn-ipsec-host` pod successfully comes up on the worker node without an error. (link:https://issues.redhat.com/browse/OCPBUGS-52951[OCPBUGS-52951])

	* Previously, the `ovn-ipsec-host` pod experienced a crash loop on RHEL worker nodes because of a missing shared library during the container execution. With this release, the `ovn-ipsec-host` pod successfully comes up on the worker node without an error. (link:https://issues.redhat.com/browse/OCPBUGS-52951[OCPBUGS-52951])
	* Previously, the `ovn-ipsec-host` pod failed with a crash loop on RHEL worker nodes because of a missing shared library during the container execution. With this release, the `ovn-ipsec-host` pod successfully starts on the worker node without an error. (link:https://issues.redhat.com/browse/OCPBUGS-52951[OCPBUGS-52951])


		* Previously, the `ovn-ipsec-host` pod experienced a crash loop on RHEL worker nodes because of a missing shared library during the container execution. With this release, the `ovn-ipsec-host` pod successfully comes up on the worker node without an error. (link:https://issues.redhat.com/browse/OCPBUGS-52951[OCPBUGS-52951])

		* Previously, the {olm-first} CSV annotation contained unexpected JSON, which was successfully parsed, but then resulted in a runtime error when attempting to use the resulting value. With this release, JSON values from OLM annotations are validated before use, errors are logged, and the console does not fail when an unexpected JSON is received in an annotation. (link:https://issues.redhat.com/browse/OCPBUGS-51277[(OCPBUGS-51277)])

	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].
	To update a cluster from an earlier {product-title} version to this version, 4.17.24, see xref:../updating/updating_a_cluster/updating-cluster-cli.adoc#updating-cluster-cli[Updating a cluster using the CLI].

OSDOCS#13971: Update the z-stream RNs for 4.17.24 #91900

OSDOCS#13971: Update the z-stream RNs for 4.17.24 #91900

Conversation

tmalove commented Apr 9, 2025 • edited Loading

ocpdocs-previewbot commented Apr 9, 2025 • edited Loading

tmalove commented Apr 9, 2025

max-cx commented Apr 9, 2025

max-cx left a comment • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

max-cx Apr 9, 2025 • edited Loading

Choose a reason for hiding this comment

max-cx commented Apr 9, 2025

tmalove commented Apr 9, 2025

tmalove commented Apr 9, 2025

Choose a reason for hiding this comment

openshift-ci bot commented Apr 9, 2025

tmalove commented Apr 9, 2025 •

edited

Loading

ocpdocs-previewbot commented Apr 9, 2025 •

edited

Loading

max-cx left a comment •

edited

Loading

max-cx Apr 9, 2025 •

edited

Loading