Skip to content

OCPBUGS-57348: release_notes/ocp-4-19-release-notes: Add a boot-image-clobber known issue #94987

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
wants to merge 1 commit into
base: enterprise-4.19
Choose a base branch
from
Open

OCPBUGS-57348: release_notes/ocp-4-19-release-notes: Add a boot-image-clobber known issue #94987

wants to merge 1 commit into from
+2 −0

Conversation

wking
Copy link
Member

@wking wking commented Jun 18, 2025 •
edited
Loading

OCPBUGS-57348 is the 4.20 bug, and we don't have a 4.19.z clone yet, but we can update this entry once that 4.19.z OCPBUGS-... exists.

Version(s): 4.19

Issue: OCPBUGS-57348

Docs preview.

QE review:

  • QE has approved this change.

@openshift-ci-robot openshift-ci-robot added jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. labels Jun 18, 2025
@openshift-ci-robot
Copy link

@wking: This pull request references Jira Issue OCPBUGS-57348, which is invalid:

  • expected Jira Issue OCPBUGS-57348 to depend on a bug in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

OCPBUGS-57348 is the 4.20 bug, and we don't have a 4.19.z clone yet, but we can update this entry once that 4.19.z OCPBUGS-... exists.

Version(s): 4.19

Issue: [OCPBUGS-57348](https://issues.redhat.com/browse/OCPBUGS-57348

Link to docs preview:

QE review:

  • QE has approved this change.

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-robot openshift-ci-robot added the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Jun 18, 2025
@openshift-ci openshift-ci bot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Jun 18, 2025
@wking
Copy link
Member Author

wking commented Jun 18, 2025

@openshift/team-documentation, I'm not sure what the add-a-known-issue process is; can you help me get this ingested?

@ocpdocs-previewbot
Copy link

ocpdocs-previewbot commented Jun 18, 2025 •
edited
Loading

🤖 Wed Jun 18 23:45:47 - Prow CI generated the docs preview:

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

@wking wking force-pushed the boot-image-clobber-known-issue branch from df43ab0 to 72d6586 Compare June 18, 2025 23:27
@wking
release_notes/ocp-4-19-release-notes: Add a boot-image-clobber known …
72d6586 
…issue

https://issues.redhat.com/browse/OCPBUGS-57348 is the 4.20 bug, and we
don't have a 4.19.z clone yet, but we can update this entry once that
4.19.z OCPBUGS-... exists.
@openshift-ci OpenShift CI
Copy link

openshift-ci bot commented Jun 18, 2025

@wking: 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.

dfitzmau
dfitzmau reviewed Jun 19, 2025
View reviewed changes
release_notes/ocp-4-19-release-notes.adoc
@@ -2741,6 +2741,8 @@ In the following tables, features are marked with the following statuses:

* In {product-title} {product-version}, clusters using IPsec for network encryption might experience intermittent loss of pod-to-pod connectivity. This prevents some pods on certain nodes from reaching services on other nodes, resulting in connection timeouts. Internal testing could not reproduce this issue on clusters with 120 nodes or less. There is no workaround for this issue. (link:https://issues.redhat.com/browse/OCPBUGS-55453[OCPBUGS-55453])

* {product-title} clusters that are installed on {aws-short} with custom AMIs or on {gcp-short} with custom disk images will have those customizations overridden by boot image management. To recover, you must xref:../machine_configuration/mco-update-boot-images.adoc#mco-update-boot-images-disable_machine-configs-configure[disable boot image management], restore your MachineSet boot images, and delete any Machines created with an undesired boot image.(link:https://issues.redhat.com/browse/OCPBUGS-57348[OCPBUGS-57348])
Copy link
Contributor

@dfitzmau dfitzmau Jun 19, 2025 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
* {product-title} clusters that are installed on {aws-short} with custom AMIs or on {gcp-short} with custom disk images will have those customizations overridden by boot image management. To recover, you must xref:../machine_configuration/mco-update-boot-images.adoc#mco-update-boot-images-disable_machine-configs-configure[disable boot image management], restore your MachineSet boot images, and delete any Machines created with an undesired boot image.(link:https://issues.redhat.com/browse/OCPBUGS-57348[OCPBUGS-57348])
* If you install a cluster on {aws-short} that has Amazon Machine Images (AMI) enabled or on {gcp-short} that has custom disk images enabled, the boot image management overrides these customization images with boot images. As a workaround, you can disable the boot image management feature, restore the boot images for the machine sets to their original location, and delete any machines that were incorrectly generated by the overriding boot images. To disable boot image management, see ref:../machine_configuration/mco-update-boot-images.adoc#mco-update-boot-images-disable_machine-configs-configure[disable boot image management]. (link:https://issues.redhat.com/browse/OCPBUGS-57348[OCPBUGS-57348])

@dfitzmau dfitzmau added the peer-review-done Signifies that the peer review team has reviewed this PR label Jun 19, 2025
@dfitzmau
Copy link
Contributor

Thanks for raising this PR, @wking . I added a comment that revised the note.

@dfitzmau
Copy link
Contributor

When incorporated exactly as is or some variant, you can add a /label merge-review-needed comment to this PR, to place the PR in the merge queue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@dfitzmau dfitzmau dfitzmau approved these changes

Assignees
No one assigned
Labels
branch/enterprise-4.19 jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. peer-review-done Signifies that the peer review team has reviewed this PR size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
4 participants
@wking @openshift-ci-robot @ocpdocs-previewbot @dfitzmau