OSDOCS-18070: Adding known issue for bare metal firmware updates #105593
Conversation
openshift-ci
bot
added
the
size/S
| * Currently, pods that use a `guaranteed` QoS class and request whole CPUs might not restart automatically after a node reboot or kubelet restart. The issue might occur in nodes configured with a static CPU Manager policy and using the `full-pcpus-only` specification, and when most or all CPUs on the node are already allocated by such workloads. As a workaround, manually delete and re-create the affected pods. (link:https://issues.redhat.com/browse/OCPBUGS-43280[OCPBUGS-43280]) | ||
|
|
||
| * On systems using specific AMD EPYC processors, some low-level system interrupts, for example `AMD-Vi`, might contain CPUs in the CPU mask that overlaps with CPU-pinned workloads. This behavior is because of the hardware design. These specific error-reporting interrupts are generally inactive and there is currently no known performance impact.(link:https://issues.redhat.com/browse/OCPBUGS-57787[OCPBUGS-57787]) No newline at end of file | ||
| * On systems using specific AMD EPYC processors, some low-level system interrupts, for example `AMD-Vi`, might contain CPUs in the CPU mask that overlaps with CPU-pinned workloads. This behavior is because of the hardware design. These specific error-reporting interrupts are generally inactive and there is currently no known performance impact.(link:https://issues.redhat.com/browse/OCPBUGS-57787[OCPBUGS-57787]) |
There was a problem hiding this comment.
ignore this bit; erroneously marked as a change from previous bullet
abhatt-rh
changed the title
openshift-ci-robot
added
the
jira/valid-reference
|
@abhatt-rh: This pull request references OSDOCS-18070 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. |
|
@abhatt-rh: This pull request references OSDOCS-18070 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. |
1 similar comment
|
@abhatt-rh: This pull request references OSDOCS-18070 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. |
|
🤖 Wed Jan 28 19:45:58 - Prow CI generated the docs preview: |
|
@abhatt-rh: This pull request references OSDOCS-18070 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. |
| * If the issue persists, deleting the Ironic pod. | ||
| -- | ||
| + | ||
| A native abort capability for servicing operations might be planned for a future release. No newline at end of file |
There was a problem hiding this comment.
Might want to add this as well:
"If these steps are unsuccessful, contact your bare-metal hardware vendor for additional support."
|
/retest |
|
@abhatt-rh: The following test failed, say
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. |
|
@abhatt-rh generally |
I did not find a precedence of adding admonitions (warning/important/note) to Known Issues in release note. However, I do see that we have called them out as warnings in the main docs sections:
Additionally, we add a reference to these from the release notes' New features and enhancement where we announce the GA So, I think we have sufficiently drawn attention to this known issue. |
|
/lgtm |
6 participants
OSDOCS-18070: Adding known issue for bare metal firmware updates
Version(s):
enterprise-4.21 only
Issue:
https://issues.redhat.com/browse/OSDOCS-18070
Link to docs preview:
https://105593--ocpdocs-pr.netlify.app/openshift-enterprise/latest/release_notes/ocp-4-21-release-notes.html#rn-ocp-release-notes-known-issues_release-notes:~:text=While%20Day%202%20firmware
QE review: