MULTIARCH-6267 MTO 1.3.2 release notes#115221
Open
bscott-rh wants to merge 1 commit into
Open
Conversation
openshift-ci
Bot
added
the
size/S
|
🤖 Mon Jul 13 19:47:44 - Prow CI generated the docs preview: |
bscott-rh
force-pushed
the
MULTIARCH-6267
branch
from
8011eb5 to
affc816
Compare
bscott-rh
force-pushed
the
MULTIARCH-6267
branch
from
affc816 to
d80ee49
Compare
|
@bscott-rh: 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. |
| [id="multi-arch-tuning-operator-1-3-2-bug-fixes_{context}"] | ||
| == Bug fixes | ||
|
|
||
| * Previously, when deleting a `ClusterPodPlacementConfig` with the `execFormatErrorMonitor` plugin enabled, the MTO remained stuck in `Deleting` state because some resources were not deleted. With this update, all relevant resources are removed so that the deletion is successful. link:https://redhat.atlassian.net/browse/MULTIARCH-6186[(*MULTIARCH-6186*)] |
There was a problem hiding this comment.
Suggested change
| * Previously, when deleting a `ClusterPodPlacementConfig` with the `execFormatErrorMonitor` plugin enabled, the MTO remained stuck in `Deleting` state because some resources were not deleted. With this update, all relevant resources are removed so that the deletion is successful. link:https://redhat.atlassian.net/browse/MULTIARCH-6186[(*MULTIARCH-6186*)] | |
| * Previously, when deleting a `ClusterPodPlacementConfig` with the `execFormatErrorMonitor` plugin enabled, the MTO could get stuck in a `Deleting` state because some resources were not deleted. With this update, all relevant resources are removed so that the deletion is successful. link:https://redhat.atlassian.net/browse/MULTIARCH-6186[(*MULTIARCH-6186*)] |
|
|
||
| * Previously, when deleting a `ClusterPodPlacementConfig` with the `execFormatErrorMonitor` plugin enabled, the MTO remained stuck in `Deleting` state because some resources were not deleted. With this update, all relevant resources are removed so that the deletion is successful. link:https://redhat.atlassian.net/browse/MULTIARCH-6186[(*MULTIARCH-6186*)] | ||
|
|
||
| * Previously, a race condition prevented the `execFormatErrorMonitor` from successfully recording `eNoExecEvent` errors when an architecture mismatch was present. With this update, errors are recorded successfully. link:https://redhat.atlassian.net/browse/MULTIARCH-6207[(*MULTIARCH-6207*)] |
There was a problem hiding this comment.
Suggested change
| * Previously, a race condition prevented the `execFormatErrorMonitor` from successfully recording `eNoExecEvent` errors when an architecture mismatch was present. With this update, errors are recorded successfully. link:https://redhat.atlassian.net/browse/MULTIARCH-6207[(*MULTIARCH-6207*)] | |
| * Previously, a race condition between the eNoExecEvent daemon and the handler controller caused ENoExecEvent CR to be rolled back before its status could be set, preventing any exec format errors from being recorded. This update resolves the conflict so events are captured successfully. link:https://redhat.atlassian.net/browse/MULTIARCH-6207[(*MULTIARCH-6207*)] |
|
|
||
| * Previously, a race condition prevented the `execFormatErrorMonitor` from successfully recording `eNoExecEvent` errors when an architecture mismatch was present. With this update, errors are recorded successfully. link:https://redhat.atlassian.net/browse/MULTIARCH-6207[(*MULTIARCH-6207*)] | ||
|
|
||
| * Previously, when deleting a `ClusterPodPlacementConfig` when `PodPlacementConfig` resources still existed, the `PodPlacementConfig` resources were inadvertently deleted. With this update, the `ClusterPodPlacementConfig` deletion is blocked so that existing resources are preserved. link:https://redhat.atlassian.net/browse/MULTIARCH-6236[(*MULTIARCH-6236*)] |
There was a problem hiding this comment.
Suggested change
| * Previously, when deleting a `ClusterPodPlacementConfig` when `PodPlacementConfig` resources still existed, the `PodPlacementConfig` resources were inadvertently deleted. With this update, the `ClusterPodPlacementConfig` deletion is blocked so that existing resources are preserved. link:https://redhat.atlassian.net/browse/MULTIARCH-6236[(*MULTIARCH-6236*)] | |
| * Previously, deleting a ClusterPodPlacementConfig could tear down the webhook and operand resources while PodPlacementConfigs still existed, orphaning them without the resources they depend on. The deletion is now properly gated and blocks if any PodPlacementConfigs remain. link:https://redhat.atlassian.net/browse/MULTIARCH-6236[(*MULTIARCH-6236*)] |
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
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.22+
Issue:
https://redhat.atlassian.net/browse/MULTIARCH-6267
Link to docs preview:
https://115221--ocpdocs-pr.netlify.app/openshift-enterprise/latest/post_installation_configuration/configuring-multi-arch-compute-machines/multi-arch-tuning-operator-release-notes.html#multi-arch-tuning-operator-release-notes-1-3-2_multi-arch-tuning-operator-release-notes
QE review: