OSDOCS-15112:Update the z-stream RNs for 4.18.19 #95465
Conversation
openshift-ci-robot
added
the
jira/valid-reference
|
@tedaveryredhat: This pull request references OSDOCS-15112 which is a valid jira issue. In response to this:
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 openshift-eng/jira-lifecycle-plugin repository. |
openshift-ci
bot
added
the
size/M
|
🤖 Wed Jul 02 14:00:58 - Prow CI generated the docs preview: |
|
@tedaveryredhat: This pull request references OSDOCS-15112 which is a valid jira issue. In response to this:
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 openshift-eng/jira-lifecycle-plugin repository. |
tedaveryredhat
force-pushed
the
OSDOCS-15112
branch
from
c85928b to
cceb7fc
Compare
|
/label peer-review-needed |
|
@tedaveryredhat: This pull request references OSDOCS-15112 which is a valid jira issue. In response to this:
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 openshift-eng/jira-lifecycle-plugin repository. |
openshift-ci
bot
added
the
peer-review-needed
JoeAldinger
added
peer-review-in-progress
| @@ -3023,6 +3023,36 @@ 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.18.19 | |||
| [id="ocp-4-18-19_{context}"] | |||
| === RHSA-2025:9725 - {product-title} {product-version}.18 bug fix and security update | |||
There was a problem hiding this comment.
| === RHSA-2025:9725 - {product-title} {product-version}.18 bug fix and security update | |
| === RHSA-2025:9725 - {product-title} {product-version}.19 bug fix and security update |
There was a problem hiding this comment.
Sorry, I just saw this typo
|
|
||
| Issued: 2 July 2025 | ||
|
|
||
| {product-title} release {product-version}.18 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:9725[RHSA-2025:9725] advisory. The RPM packages that are included in the update are provided by the link:https://access.redhat.com/errata/RHSA-2025:9726[RHSA-2025:9726] advisory. |
There was a problem hiding this comment.
| {product-title} release {product-version}.18 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:9725[RHSA-2025:9725] advisory. The RPM packages that are included in the update are provided by the link:https://access.redhat.com/errata/RHSA-2025:9726[RHSA-2025:9726] advisory. | |
| {product-title} release {product-version}.19 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:9725[RHSA-2025:9725] advisory. The RPM packages that are included in the update are provided by the link:https://access.redhat.com/errata/RHSA-2025:9726[RHSA-2025:9726] advisory. |
JoeAldinger
added
peer-review-done
|
|
||
| * Previously, the `oc adm node-image create` command incorrectly modified the existing permissions of the target assets folder when the command saved the artifacts on the disk. With this release, a bug fix ensures that the copying operation for the command keeps the destination folder permissions. (link:https://issues.redhat.com/browse/OCPBUGS-57507[OCPBUGS-57507]) | ||
|
|
||
| * Previously, Prometheus v3 did not support Alertmanager v1, which caused early failures when you specified `apiVersion v1` in config maps. With this release, the Alertmanager API Version is updated from v1 to v2 in the config maps to prevent `InvalidConfig` errors. As a result, the `InvalidConfig` errors do not occur when you upgrade to {product-title} version 4.19. (link:https://issues.redhat.com/browse/OCPBUGS-56251[OCPBUGS-56251]) |
There was a problem hiding this comment.
Hello @tedaveryredhat 👋 my engineers let me know about the last minute change to this release note, they updated the Jira with what they consider correct now: https://issues.redhat.com/browse/OCPBUGS-56251
Do you want me to wait until this is merged and create a quick fix, or can this still be updated in this PR?
Thanks!
There was a problem hiding this comment.
This content can still be updated in this PR. I'm going to commit the new content this morning.
tedaveryredhat
force-pushed
the
OSDOCS-15112
branch
from
cceb7fc to
59bf41c
Compare
|
New changes are detected. LGTM label has been removed. |
|
|
||
| * Previously, the `oc adm node-image create` command incorrectly modified the existing permissions of the target assets folder when the command saved the artifacts on the disk. With this release, a bug fix ensures that the copying operation for the command keeps the destination folder permissions. (link:https://issues.redhat.com/browse/OCPBUGS-57507[OCPBUGS-57507]) | ||
|
|
||
| * Previously, using Alertmanager apiVersion v1 in the `openshift-monitoring/cluster-monitoring-config` or `openshift-user-workload-monitoring/user-workload-monitoring-config` parameters caused {product-title} 4.19 to fail early with an `InvalidConfigXXX` error. This issue occurred because {product-title} 4.19 is using Prometheus v3 which does not support Alertmanager apiVersion v1. With this release, {cmo-first} sets `upgradable=false` if apiVersion v1 is detected in the config maps to prevent the `InvalidConfigXXX` error from occurring after upgrading to {product-title} 4.19. As a result, clusters upgrade through {product-title} 4.18.x before moving to {product-title} 4.19. (link:https://issues.redhat.com/browse/OCPBUGS-56251[OCPBUGS-56251]) |
There was a problem hiding this comment.
| * Previously, using Alertmanager apiVersion v1 in the `openshift-monitoring/cluster-monitoring-config` or `openshift-user-workload-monitoring/user-workload-monitoring-config` parameters caused {product-title} 4.19 to fail early with an `InvalidConfigXXX` error. This issue occurred because {product-title} 4.19 is using Prometheus v3 which does not support Alertmanager apiVersion v1. With this release, {cmo-first} sets `upgradable=false` if apiVersion v1 is detected in the config maps to prevent the `InvalidConfigXXX` error from occurring after upgrading to {product-title} 4.19. As a result, clusters upgrade through {product-title} 4.18.x before moving to {product-title} 4.19. (link:https://issues.redhat.com/browse/OCPBUGS-56251[OCPBUGS-56251]) | |
| * Previously, using Alertmanager apiVersion v1 in the `openshift-monitoring/cluster-monitoring-config` or `openshift-user-workload-monitoring/user-workload-monitoring-config` parameters caused {product-title} 4.19 to fail early with an `InvalidConfigXXX` error. This issue occurred because {product-title} 4.19 is using Prometheus v3 which does not support Alertmanager apiVersion v1. With this release, {cmo-first} sets a value of `upgradable=false` if apiVersion v1 is detected in the config maps to prevent the `InvalidConfigXXX` error from occurring after upgrading to {product-title} 4.19. As a result, clusters upgrade through {product-title} 4.18.x before moving to {product-title} 4.19. (link:https://issues.redhat.com/browse/OCPBUGS-56251[OCPBUGS-56251]) |
tedaveryredhat
force-pushed
the
OSDOCS-15112
branch
from
59bf41c to
bfcf64a
Compare
|
@tedaveryredhat: 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. |
|
/label merge-review-needed |
JoeAldinger
added
the
merge-review-in-progress
Version(s):
4.18
Issue:
https://issues.redhat.com/browse/OSDOCS-15112
Link to docs preview:
https://95465--ocpdocs-pr.netlify.app/openshift-enterprise/latest/release_notes/ocp-4-18-release-notes.html