OSDOCS#12512: Update the release notes for the 4.13.53 z-stream #84508
Conversation
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
openshift-ci
bot
added
the
size/S
|
🤖 Thu Nov 07 14:12:52 - Prow CI generated the docs preview: |
|
/label peer-review-needed |
openshift-ci
bot
added
the
peer-review-needed
dfitzmau
added
peer-review-in-progress
dfitzmau
reviewed
Nov 6, 2024
| [id="ocp-4-13-53-bug-fixes"] | ||
| ==== Bug fixes | ||
|
|
||
| * Previously, because of a {gcp-first} change, the Cloud Credential Operator (CCO) becomes degraded. With this release, `CredentialsRequests` is updated to set `skipServiceCheck`, and the CCO is not degraded. (link:https://issues.redhat.com/browse/OCPBUGS-43856[*OCPBUGS-43856*]) |
There was a problem hiding this comment.
When I contacted Trevor, the note took a bit of a slightly different angle.
See https://issues.redhat.com/browse/OCPBUGS-43821 and #84485. I'd recommend checking with Trevor.
dfitzmau
added
peer-review-done
dfitzmau
approved these changes
Nov 6, 2024
tmalove
force-pushed
the
OSDOCS-12512
branch
2 times, most recently
from
0f05f45 to
43c2738
Compare
|
/label merge-review-needed |
openshift-ci
bot
added
the
merge-review-needed
skopacz1
added
the
merge-review-in-progress
skopacz1
reviewed
Nov 6, 2024
| To update an existing {product-title} 4.13 cluster to this latest release, see xref:../updating/updating-cluster-cli.adoc#updating-cluster-cli[Updating a cluster using the CLI]. | ||
|
|
||
| // 4.13.53 | ||
| [id="ocp-4-13-53"] |
There was a problem hiding this comment.
All IDs that are not the top ID of an assembly need to have a context at the end:
Suggested change
| [id="ocp-4-13-53"] | |
| [id="ocp-4-13-53_{context}"] |
| $ oc adm release info 4.13.53 --pullspecs | ||
| ---- | ||
|
|
||
| [id="ocp-4-13-53-bug-fixes"] |
There was a problem hiding this comment.
Same comment about adding a context
|
|
||
| * Previously, upgrading to {product-title} 4.14 triggered service disruptions in applications that set duplicate `Transfer-Encoding` headers. This resulted in rejected responses, including a gateway error, which affected customer service. With this release, cluster administrators can use a procedure to detect applications that send duplicate `Transfer-Encoding` headers before upgrading to {product-title} 4.13. Any issues can be corrected before causing service disruption.. (link:https://issues.redhat.com/browse/OCPBUGS-43095[*OCPBUGS-43095*]) | ||
|
|
||
| [id="ocp-4-13-53-updating"] |
There was a problem hiding this comment.
Same comment about adding a context
| [id="ocp-4-13-53-bug-fixes"] | ||
| ==== Bug fixes | ||
|
|
||
| * Previously, the Cloud Credential Operator (CCO) for a cluster installed on {gcp-first} was degraded. {gcp-short} clusters that were not in manual mode thought they needed the `backupdr` permissions. However, in accounts where the `backupdr` API was not enabled, the clusters correctly determined that they did not have those permissions. Manual mode {gcp-short} clusters were not affected. With this release, the `skipServiceCheck` parameter is set to `true` on the `CredentialsRequest` custom resource (CR), so this issue no longer occurs. (link:https://issues.redhat.com/browse/OCPBUGS-43856[*OCPBUGS-43856*]) |
There was a problem hiding this comment.
I think "thought they needed" is a little anthropomorphic. If you think this would still be accurate, I'd suggest changing the wording to something like this:
Suggested change
| * Previously, the Cloud Credential Operator (CCO) for a cluster installed on {gcp-first} was degraded. {gcp-short} clusters that were not in manual mode thought they needed the `backupdr` permissions. However, in accounts where the `backupdr` API was not enabled, the clusters correctly determined that they did not have those permissions. Manual mode {gcp-short} clusters were not affected. With this release, the `skipServiceCheck` parameter is set to `true` on the `CredentialsRequest` custom resource (CR), so this issue no longer occurs. (link:https://issues.redhat.com/browse/OCPBUGS-43856[*OCPBUGS-43856*]) | |
| * Previously, the Cloud Credential Operator (CCO) for a cluster installed on {gcp-first} was degraded. {gcp-short} clusters that were not in manual mode incorrectly required `backupdr` permissions. However, in accounts where the `backupdr` API was not enabled, the clusters correctly determined that they did not have those permissions. Manual mode {gcp-short} clusters were not affected. With this release, the `skipServiceCheck` parameter is set to `true` on the `CredentialsRequest` custom resource (CR), so this issue no longer occurs. (link:https://issues.redhat.com/browse/OCPBUGS-43856[*OCPBUGS-43856*]) |
|
|
||
| * Previously, the Cloud Credential Operator (CCO) for a cluster installed on {gcp-first} was degraded. {gcp-short} clusters that were not in manual mode thought they needed the `backupdr` permissions. However, in accounts where the `backupdr` API was not enabled, the clusters correctly determined that they did not have those permissions. Manual mode {gcp-short} clusters were not affected. With this release, the `skipServiceCheck` parameter is set to `true` on the `CredentialsRequest` custom resource (CR), so this issue no longer occurs. (link:https://issues.redhat.com/browse/OCPBUGS-43856[*OCPBUGS-43856*]) | ||
|
|
||
| * Previously, upgrading to {product-title} 4.14 triggered service disruptions in applications that set duplicate `Transfer-Encoding` headers. This resulted in rejected responses, including a gateway error, which affected customer service. With this release, cluster administrators can use a procedure to detect applications that send duplicate `Transfer-Encoding` headers before upgrading to {product-title} 4.13. Any issues can be corrected before causing service disruption.. (link:https://issues.redhat.com/browse/OCPBUGS-43095[*OCPBUGS-43095*]) |
There was a problem hiding this comment.
Update is the preferred term:
Suggested change
| * Previously, upgrading to {product-title} 4.14 triggered service disruptions in applications that set duplicate `Transfer-Encoding` headers. This resulted in rejected responses, including a gateway error, which affected customer service. With this release, cluster administrators can use a procedure to detect applications that send duplicate `Transfer-Encoding` headers before upgrading to {product-title} 4.13. Any issues can be corrected before causing service disruption.. (link:https://issues.redhat.com/browse/OCPBUGS-43095[*OCPBUGS-43095*]) | |
| * Previously, updating to {product-title} 4.14 triggered service disruptions in applications that set duplicate `Transfer-Encoding` headers. This resulted in rejected responses, including a gateway error, which affected customer service. With this release, cluster administrators can use a procedure to detect applications that send duplicate `Transfer-Encoding` headers before updating to {product-title} 4.13. Any issues can be corrected before causing service disruption.. (link:https://issues.redhat.com/browse/OCPBUGS-43095[*OCPBUGS-43095*]) |
|
|
||
| * Previously, the Cloud Credential Operator (CCO) for a cluster installed on {gcp-first} was degraded. {gcp-short} clusters that were not in manual mode thought they needed the `backupdr` permissions. However, in accounts where the `backupdr` API was not enabled, the clusters correctly determined that they did not have those permissions. Manual mode {gcp-short} clusters were not affected. With this release, the `skipServiceCheck` parameter is set to `true` on the `CredentialsRequest` custom resource (CR), so this issue no longer occurs. (link:https://issues.redhat.com/browse/OCPBUGS-43856[*OCPBUGS-43856*]) | ||
|
|
||
| * Previously, upgrading to {product-title} 4.14 triggered service disruptions in applications that set duplicate `Transfer-Encoding` headers. This resulted in rejected responses, including a gateway error, which affected customer service. With this release, cluster administrators can use a procedure to detect applications that send duplicate `Transfer-Encoding` headers before upgrading to {product-title} 4.13. Any issues can be corrected before causing service disruption.. (link:https://issues.redhat.com/browse/OCPBUGS-43095[*OCPBUGS-43095*]) |
There was a problem hiding this comment.
extra period here:
Suggested change
| * Previously, upgrading to {product-title} 4.14 triggered service disruptions in applications that set duplicate `Transfer-Encoding` headers. This resulted in rejected responses, including a gateway error, which affected customer service. With this release, cluster administrators can use a procedure to detect applications that send duplicate `Transfer-Encoding` headers before upgrading to {product-title} 4.13. Any issues can be corrected before causing service disruption.. (link:https://issues.redhat.com/browse/OCPBUGS-43095[*OCPBUGS-43095*]) | |
| * Previously, upgrading to {product-title} 4.14 triggered service disruptions in applications that set duplicate `Transfer-Encoding` headers. This resulted in rejected responses, including a gateway error, which affected customer service. With this release, cluster administrators can use a procedure to detect applications that send duplicate `Transfer-Encoding` headers before upgrading to {product-title} 4.13. Any issues can be corrected before causing service disruption. (link:https://issues.redhat.com/browse/OCPBUGS-43095[*OCPBUGS-43095*]) |
|
@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. |
skopacz1
removed
merge-review-in-progress
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.13
Issue:
OSDOCS-12512
Link to docs preview:
4.13.53
QE review:
n/a