OSDOCS-20775: Add 4.18.49 z-stream release notes - #115968
Conversation
openshift-ci-robot
added
the
jira/valid-reference
|
@tedaveryredhat: This pull request references OSDOCS-20775 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. |
openshift-ci
Bot
added
the
do-not-merge/work-in-progress
|
Skipping CI for Draft Pull Request. |
openshift-ci
Bot
added
the
size/M
ba8b683 to
55f33d4
Compare
openshift-ci
Bot
removed
the
do-not-merge/work-in-progress
|
/test all |
55f33d4 to
6b356d9
Compare
|
🤖 Wed Jul 22 15:33:35 - Prow CI generated the docs preview: |
| [id="zstream-4-18-49-updating_{context}"] | ||
| == Updating | ||
|
|
||
| To update an {product-title} 4.18 cluster to this latest release, see xref:../updating/updating_a_cluster/updating-cluster-cli.adoc#updating-cluster-cli[Updating a cluster using the CLI]. |
There was a problem hiding this comment.
🤖 [error] OpenShiftAsciiDoc.NoXrefInModules: Do not include xrefs in modules, only assemblies (exception: release notes modules).
|
@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. |
|
/label merge-review-needed |
openshift-ci
Bot
added
the
merge-review-needed
mburke5678
added
the
merge-review-in-progress
| [id="zstream-4-18-49-enhancements_{context}"] | ||
| == Enhancements | ||
|
|
||
| * Before this update, deleting a BareMetalHost (BMH) that referenced a pre-provisioning network data Secret through the `spec.preprovisioningNetworkDataName` parameter could report a `RegistrationError` if the Secret was removed before the BMH finished deleting. As a consequence, the BMH deletion would take minutes to complete before an eventual force-delete by the controller. With this release, the Bare Metal Operator (BMO) manages the lifecycle of that Secret in the same way as the BMC credential Secrets. The BMO now protects the Secret using a finalizer while the host is active, which prevents the Secret deletion until the finalizer is removed by the controller. As a result, the BMH is removed successfully before the Secret is allowed to be deleted. (link:https://redhat.atlassian.net/browse/OCPBUGS-87967[OCPBUGS-87967]) |
There was a problem hiding this comment.
Changes for a follow up PR?
Doc Guidelines: When referring to API object terms in general usage, use lowercase and separate multi-word API objects.
| * Before this update, deleting a BareMetalHost (BMH) that referenced a pre-provisioning network data Secret through the `spec.preprovisioningNetworkDataName` parameter could report a `RegistrationError` if the Secret was removed before the BMH finished deleting. As a consequence, the BMH deletion would take minutes to complete before an eventual force-delete by the controller. With this release, the Bare Metal Operator (BMO) manages the lifecycle of that Secret in the same way as the BMC credential Secrets. The BMO now protects the Secret using a finalizer while the host is active, which prevents the Secret deletion until the finalizer is removed by the controller. As a result, the BMH is removed successfully before the Secret is allowed to be deleted. (link:https://redhat.atlassian.net/browse/OCPBUGS-87967[OCPBUGS-87967]) | |
| * Before this update, deleting a bare metal host (BMH) that referenced a pre-provisioning network data secret, through the `spec.preprovisioningNetworkDataName` parameter, could report a `RegistrationError` if the secret was removed before the BMH finished deleting. As a consequence, the BMH deletion would take minutes to complete before an eventual force-delete by the controller. With this release, the Bare Metal Operator (BMO) manages the lifecycle of that Secret in the same way as the BMC credential secrets. The BMO now protects the secret using a finalizer while the host is active, which prevents the secret deletion until the finalizer is removed by the controller. As a result, the BMH is removed successfully before the secret is allowed to be deleted. (link:https://redhat.atlassian.net/browse/OCPBUGS-87967[OCPBUGS-87967]) |
mburke5678
removed
merge-review-in-progress
5 participants
Version(s):
4.18
Issue:
https://redhat.atlassian.net/browse/OSDOCS-20775
Link to docs preview:
https://115968--ocpdocs-pr.netlify.app/openshift-enterprise/latest/release_notes/ocp-4-18-release-notes.html#zstream-4-18-49_release-notes
QE review:
N/A
Additional information: