OSDOCS-14033: Release Note for 4.15.49#92106
Merged
jeana-redhat merged 1 commit intoopenshift:enterprise-4.15from Apr 17, 2025
Merged
OSDOCS-14033: Release Note for 4.15.49#92106jeana-redhat merged 1 commit intoopenshift:enterprise-4.15from
jeana-redhat merged 1 commit intoopenshift:enterprise-4.15from
Conversation
openshift-ci
bot
added
the
size/S
|
🤖 Thu Apr 17 14:59:03 - Prow CI generated the docs preview: |
dfitzmau
changed the title
openshift-ci-robot
added
the
jira/valid-reference
|
@tedaveryredhat: This pull request references OSDOCS-14033 which is a valid jira issue. DetailsIn 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. |
dfitzmau
added
branch/enterprise-4.15
and removed
jira/valid-reference
dfitzmau
reviewed
Apr 14, 2025
Comment on lines
2783
to
2784
| [id="ocp-4-15-49_{context}"] | ||
| === RHSA-2025:3055 - {product-title} 4.15.49 bug fix and security update |
Contributor
There was a problem hiding this comment.
Suggested change
| [id="ocp-4-15-49_{context}"] | |
| === RHSA-2025:3055 - {product-title} 4.15.49 bug fix and security update | |
| [id="ocp-4-15-49_{context}"] | |
| === RHSA-2025:3790 - {product-title} 4.15.49 bug fix and security update |
This needs to be the Images advisory: https://errata.devel.redhat.com/advisory/148010
|
|
||
| Issued: 16 April 2025 | ||
|
|
||
| {product-title} release 4.15.49, which includes security updates, is now available. The list of bug fixes that are included in this update is documented in the link:https://access.redhat.com/errata/RHSA-2025:3055[RHSA-2025:3055] advisory. The RPM packages that are included in this update are provided by the link:https://access.redhat.com/errata/RHBA-2025:3057[RHBA-2025:3057] advisory. |
Contributor
There was a problem hiding this comment.
Suggested change
| {product-title} release 4.15.49, which includes security updates, is now available. The list of bug fixes that are included in this update is documented in the link:https://access.redhat.com/errata/RHSA-2025:3055[RHSA-2025:3055] advisory. The RPM packages that are included in this update are provided by the link:https://access.redhat.com/errata/RHBA-2025:3057[RHBA-2025:3057] advisory. | |
| {product-title} release 4.15.49, which includes security updates, is now available. The list of bug fixes that are included in this update is documented in the link:https://access.redhat.com/errata/RHSA-2025:3790[RHSA-2025:3790] advisory. The RPM packages that are included in this update are provided by the link:https://access.redhat.com/errata/RHBA-2025:3792[RHBA-2025:3792] advisory. |
|
|
||
| [id="ocp-4-15-49-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 by using the CLI]. |
Contributor
There was a problem hiding this comment.
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 by using the CLI]. | |
| To update an {product-title} 4.15 cluster to this latest release, see xref:../updating/updating_a_cluster/updating-cluster-cli.adoc#updating-cluster-cli[Updating a cluster by using the CLI]. |
openshift-ci
bot
added
size/M
tmalove
reviewed
Apr 15, 2025
|
|
||
| Issued: 16 April 2025 | ||
|
|
||
| {product-title} release 4.15.49, which includes security updates, is now available. The list of bug fixes that are included in this update is documented in the link:https://access.redhat.com/errata/RHSA-2025:3055[RHSA-2025:3055] advisory. The RPM packages that are included in this update are provided by the link:https://access.redhat.com/errata/RHBA-2025:3057[RHBA-2025:3792] advisory. |
Contributor
There was a problem hiding this comment.
Suggested change
| {product-title} release 4.15.49, which includes security updates, is now available. The list of bug fixes that are included in this update is documented in the link:https://access.redhat.com/errata/RHSA-2025:3055[RHSA-2025:3055] advisory. The RPM packages that are included in this update are provided by the link:https://access.redhat.com/errata/RHBA-2025:3057[RHBA-2025:3792] advisory. | |
| {product-title} release 4.15.49, which includes security updates, is now available. The list of bug fixes that are included in this update is documented in the link:https://access.redhat.com/errata/RHSA-2025:3790[RHSA-2025:3790] advisory. The RPM packages that are included in this update are provided by the link:https://access.redhat.com/errata/RHBA-2025:3057[RHBA-2025:3792] advisory. |
tmalove
reviewed
Apr 15, 2025
| [id="ocp-4-15-49-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}, the following error occurred: |
Contributor
There was a problem hiding this comment.
Suggested change
| * 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}, the following error occurred: | |
| * Previously, an update to the {ibm-cloud-name} Cloud Internet Services (CIS) implementation impacted the upstream Terraform plugin. If you attempted to create an externally-facing cluster on {ibm-cloud-name}, the following error occurred: |
Contributor
|
@tedaveryredhat I made a couple of comments...don't forget to squash your commits before sending for peer review. Otherwise, looks good! |
tedaveryredhat
force-pushed
the
OSDOCS-14033
branch
2 times, most recently
from
1fb3c7e to
f0b9a3e
Compare
Contributor
Author
|
/label peer-review-needed |
openshift-ci
bot
added
the
peer-review-needed
jeana-redhat
added
the
peer-review-in-progress
Contributor
jeana-redhat
left a comment
jeana-redhat
left a comment
There was a problem hiding this comment.
Mostly small stuff, plus a little backport digging
/remove-label peer-review-in-progress
/remove-label peer-review-needed
/label peer-review-done
| [id="ocp-4-15-49-known-issues_{context}"] | ||
| ==== Known issues | ||
|
|
||
| * IPsec is not supported on Red Hat Enterprise Linux (RHEL) compute nodes because of a `libreswan` incompatiblility issue between a host and an `ovn-ipsec` container that exist in each compute node. (link:https://issues.redhat.com/browse/OCPBUGS-36688 [*OCPBUGS-36688*]) |
Contributor
There was a problem hiding this comment.
Suggested change
| * IPsec is not supported on Red Hat Enterprise Linux (RHEL) compute nodes because of a `libreswan` incompatiblility issue between a host and an `ovn-ipsec` container that exist in each compute node. (link:https://issues.redhat.com/browse/OCPBUGS-36688 [*OCPBUGS-36688*]) | |
| * IPsec is not supported on {op-system-base-full} compute nodes because of a `libreswan` incompatiblility issue between a host and an `ovn-ipsec` container that exist in each compute node. (link:https://issues.redhat.com/browse/OCPBUGS-36688 [*OCPBUGS-36688*]) |
| [id="ocp-4-15-49-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 externally-facing cluster on {ibm-cloud-name}, the following error occurred: |
Contributor
There was a problem hiding this comment.
Pretty sure this was correct before (if you use "externally", there would be no hyphen, but also "external-facing" seems synonymous with "externally facing")
Suggested change
| * Previously, an update to the {ibm-cloud-name} Cloud Internet Services (CIS) implementation impacted the upstream Terraform plugin. If you attempted to create an externally-facing cluster on {ibm-cloud-name}, the following error occurred: | |
| * 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}, the following error occurred: |
|
|
||
| // Awaiting approval from Marco Braga for OCPBUGS-53139 | ||
|
|
||
| * Previously, iSCSI and Fibre Channel devices attached by multipath did not resolve correctly when partitioned. This was caused by improper handling of multipath devices. With this release, a storage bug is fixed so that the partitioned multipath storage is now correctly recognized. (https://issues.redhat.com/browse/OCPBUGS-53139[*OCPBUGS-53139*]) |
Contributor
There was a problem hiding this comment.
Suggested change
| * Previously, iSCSI and Fibre Channel devices attached by multipath did not resolve correctly when partitioned. This was caused by improper handling of multipath devices. With this release, a storage bug is fixed so that the partitioned multipath storage is now correctly recognized. (https://issues.redhat.com/browse/OCPBUGS-53139[*OCPBUGS-53139*]) | |
| * Previously, iSCSI and Fibre Channel devices attached by multipath did not resolve correctly when partitioned. This was caused by improper handling of multipath devices. With this release, the partitioned multipath storage is now correctly recognized. (https://issues.redhat.com/browse/OCPBUGS-53139[*OCPBUGS-53139*]) |
|
|
||
| * Previously, iSCSI and Fibre Channel devices attached by multipath did not resolve correctly when partitioned. This was caused by improper handling of multipath devices. With this release, a storage bug is fixed so that the partitioned multipath storage is now correctly recognized. (https://issues.redhat.com/browse/OCPBUGS-53139[*OCPBUGS-53139*]) | ||
|
|
||
| * Previously, the *Cluster Settings* page would not properly render during a cluster update if the `ClusterVersion` did not receive a `Completed` update. With this release, the *Cluster Setting* page properly renders even if the `ClusterVersion` has not received a `Completed` update. (link:https://issues.redhat.com/browse/OCPBUGS-53138[*OCPBUGS-53138*]) |
Contributor
There was a problem hiding this comment.
Is "the ClusterVersion" actually "the Cluster Version Operator (CVO)"? (check with an SME but I think this is probably the case)
Suggested change
| * Previously, the *Cluster Settings* page would not properly render during a cluster update if the `ClusterVersion` did not receive a `Completed` update. With this release, the *Cluster Setting* page properly renders even if the `ClusterVersion` has not received a `Completed` update. (link:https://issues.redhat.com/browse/OCPBUGS-53138[*OCPBUGS-53138*]) | |
| * Previously, the *Cluster Settings* page would not properly render during a cluster update if the Cluster Version Operator (CVO) did not receive a `Completed` update. With this release, the *Cluster Setting* page properly renders even if the CVO has not received a `Completed` update. (link:https://issues.redhat.com/browse/OCPBUGS-53138[*OCPBUGS-53138*]) |
|
|
||
| // Awaiting approval from Marco Braga for OCPBUGS-53055 | ||
|
|
||
| * Previously, the *Observe* section on the web console did not show items contributed from plugins unless certain flags related to the monitoring were set. However, these flags prevented other plugins, such as logging, distributed tracing, network observability, and so on, from adding items to the *Observe* section. With this release, the monitoring flags are removed so that other plugins can add items to the *Observe* section. (link:https://issues.redhat.com/browse/OCPBUGS-53055[*OCPBUGS-53055*]) |
Contributor
There was a problem hiding this comment.
Suggested change
| * Previously, the *Observe* section on the web console did not show items contributed from plugins unless certain flags related to the monitoring were set. However, these flags prevented other plugins, such as logging, distributed tracing, network observability, and so on, from adding items to the *Observe* section. With this release, the monitoring flags are removed so that other plugins can add items to the *Observe* section. (link:https://issues.redhat.com/browse/OCPBUGS-53055[*OCPBUGS-53055*]) | |
| * Previously, the *Observe* section on the web console did not show items contributed from plugins unless certain flags related to monitoring were set. However, these flags prevented other plugins, such as logging, distributed tracing, network observability, and so on, from adding items to the *Observe* section. With this release, the monitoring flags are removed so that other plugins can add items to the *Observe* section. (link:https://issues.redhat.com/browse/OCPBUGS-53055[*OCPBUGS-53055*]) |
|
|
||
| * Previously, the *Observe* section on the web console did not show items contributed from plugins unless certain flags related to the monitoring were set. However, these flags prevented other plugins, such as logging, distributed tracing, network observability, and so on, from adding items to the *Observe* section. With this release, the monitoring flags are removed so that other plugins can add items to the *Observe* section. (link:https://issues.redhat.com/browse/OCPBUGS-53055[*OCPBUGS-53055*]) | ||
|
|
||
| * Previously, the ignition-server controller based on a condition.Status overloaded the KAS by updating that condition with the same message in every reconcile loop. The updates caused an overload of the KAS. With this release, the controller checks the message and validates whether it is the existing message so that the KAS is not overloaded. (link:https://issues.redhat.com/browse/OCPBUGS-50867[*OCPBUGS-50867*]) |
Contributor
There was a problem hiding this comment.
The first sentence here is weird. When I went to look at the source, I found this bug is backported from the original which had a different bug text:
Suggested change
| * Previously, the ignition-server controller based on a condition.Status overloaded the KAS by updating that condition with the same message in every reconcile loop. The updates caused an overload of the KAS. With this release, the controller checks the message and validates whether it is the existing message so that the KAS is not overloaded. (link:https://issues.redhat.com/browse/OCPBUGS-50867[*OCPBUGS-50867*]) | |
| * Previously, `IgnitionPayload` could not be generated because of a setting in the `ImageDigestMirrorSet` (IDMS) and `ImageContentSourcePolicy` (ICSP) resources. The setting caused the Kubernetes agent server to receive patch requests that continuously modified the `status.Condition` for `ignition-server` pods. With this release, the patch command does not reapply if the `status.Condition` for `ignition-server` pods is the same as the initial patch request. (link:https://issues.redhat.com/browse/OCPBUGS-50867[*OCPBUGS-50867*]) |
I don't know which is better, but since this version has already been published it might make sense to use the original text?
Contributor
Author
There was a problem hiding this comment.
I suggested the original text to the SME and he responded by providing the "ignition-server controller" information.
Contributor
There was a problem hiding this comment.
ok, if you want to use the new version can you make this sentence parse?
Previously, the ignition-server controller based on a condition.Status overloaded the KAS by updating that condition with the same message in every reconcile loop.
Looks like KAS is "Kubernetes agent server". Not sure how to read "the ignition-server controller based on a condition.Status overloaded"
openshift-ci
bot
added
peer-review-done
dfitzmau
reviewed
Apr 16, 2025
| [id="ocp-4-15-49-known-issues_{context}"] | ||
| ==== Known issues | ||
|
|
||
| * IPsec is not supported on Red Hat Enterprise Linux (RHEL) compute nodes because of a `libreswan` incompatiblility issue between a host and an `ovn-ipsec` container that exist in each compute node. (link:https://issues.redhat.com/browse/OCPBUGS-36688 [*OCPBUGS-36688*]) |
Contributor
There was a problem hiding this comment.
Suggested change
| * IPsec is not supported on Red Hat Enterprise Linux (RHEL) compute nodes because of a `libreswan` incompatiblility issue between a host and an `ovn-ipsec` container that exist in each compute node. (link:https://issues.redhat.com/browse/OCPBUGS-36688 [*OCPBUGS-36688*]) | |
| * IPsec is not supported on Red Hat Enterprise Linux (RHEL) compute nodes because of a `libreswan` incompatiblility issue between a host and an `ovn-ipsec` container that exist in each compute node. (link:https://issues.redhat.com/browse/OCPBUGS-36688[OCPBUGS-36688]) |
Please update for each bug fix link.
dfitzmau
reviewed
Apr 16, 2025
| * IPsec is not supported on Red Hat Enterprise Linux (RHEL) compute nodes because of a `libreswan` incompatiblility issue between a host and an `ovn-ipsec` container that exist in each compute node. (link:https://issues.redhat.com/browse/OCPBUGS-36688 [*OCPBUGS-36688*]) | ||
|
|
||
| [id="ocp-4-15-49-bug-fixes_{context}"] | ||
| ==== Bug fixes |
Contributor
There was a problem hiding this comment.
The release note for https://issues.redhat.com/browse/OCPBUGS-50591 is missing.
tedaveryredhat
force-pushed
the
OSDOCS-14033
branch
from
f0b9a3e to
21ec131
Compare
openshift-ci
bot
added
size/L
Contributor
Author
|
/retest |
1 similar comment
Contributor
Author
|
/retest |
Contributor
Author
|
/label merge-review-needed |
openshift-ci
bot
added
the
merge-review-needed
|
|
||
| * Previously, the *Observe* section on the web console did not show items contributed from plugins unless certain flags related to monitoring were set. However, these flags prevented other plugins, such as logging, distributed tracing, network observability, and so on, from adding items to the *Observe* section. With this release, the monitoring flags are removed so that other plugins can add items to the *Observe* section. (link:https://issues.redhat.com/browse/OCPBUGS-53055[OCPBUGS-53055]) | ||
|
|
||
| * Previously, Previously, on a condition.Status, the ignition-server controller overloaded the Kubernetes agent server (KAS) by updating that condition with the same message in every reconcile loop. The updates caused an overload of the KAS. With this release, the controller checks the message and validates whether it is the existing message so that the KAS is not overloaded. (link:https://issues.redhat.com/browse/OCPBUGS-50867[OCPBUGS-50867]) |
Contributor
There was a problem hiding this comment.
Typo here. Also, what does "on a condition.Status" mean? I'm not sure it's clear to the audience (end user) when they might encounter this issue.
Suggested change
| * Previously, Previously, on a condition.Status, the ignition-server controller overloaded the Kubernetes agent server (KAS) by updating that condition with the same message in every reconcile loop. The updates caused an overload of the KAS. With this release, the controller checks the message and validates whether it is the existing message so that the KAS is not overloaded. (link:https://issues.redhat.com/browse/OCPBUGS-50867[OCPBUGS-50867]) | |
| * Previously, on a condition.Status, the ignition-server controller overloaded the Kubernetes agent server (KAS) by updating that condition with the same message in every reconcile loop. The updates caused an overload of the KAS. With this release, the controller checks the message and validates whether it is the existing message so that the KAS is not overloaded. (link:https://issues.redhat.com/browse/OCPBUGS-50867[OCPBUGS-50867]) |
Contributor
Author
There was a problem hiding this comment.
Thanks for catching the typo. The SME is on vacation today. I searched for "condition.Status" in JIRA and found this bug that mentions the "condition.status field". I'm going to change the wording to "Previously, in the condition.Status field...".
Contributor
There was a problem hiding this comment.
Sounds reasonable! If it's a verbatim field, throw condition.status in backticks and this should be all set 🤓 Thanks for your patience!
jeana-redhat
removed
the
merge-review-needed
| + | ||
| 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-54367[OCPBUGS-54367]) | ||
|
|
||
| // Awaiting approval from Marco Braga for OCPBUGS-54353 |
Contributor
There was a problem hiding this comment.
Are the bugs with "Awaiting approval" approved? If they are approved, remove the comments. If they aren't, is it too early to merge?
Contributor
Author
There was a problem hiding this comment.
I removed the comments because they are approved.
tedaveryredhat
force-pushed
the
OSDOCS-14033
branch
from
21ec131 to
dd71920
Compare
tedaveryredhat
force-pushed
the
OSDOCS-14033
branch
from
dd71920 to
c6c8596
Compare
|
@tedaveryredhat: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions 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. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Version(s):
4.15
Issue:
https://issues.redhat.com/browse/OSDOCS-14033
Link to docs preview:
https://92106--ocpdocs-pr.netlify.app/openshift-enterprise/latest/release_notes/ocp-4-15-release-notes.html
QE review: