OCPBUGS-13634: ztp: remove accelerated container startup #1561
Conversation
openshift-ci-robot
added
jira/valid-reference
|
@tliu2021: This pull request references Jira Issue OCPBUGS-13634, which is invalid:
Comment The bug has been updated to refer to the pull request using the external bug tracker. In 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 kubernetes/test-infra repository. |
|
/jira refresh |
|
@tliu2021: This pull request references Jira Issue OCPBUGS-13634, which is invalid:
Comment In 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 kubernetes/test-infra repository. |
|
/test ci |
|
/test ci |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: imiller0, tliu2021 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
openshift-ci
bot
added
the
approved
A known issue, tracked by OCPBUGS-15102 in OCP 4.13 and 4.14, could lead to the CPU affinities not resetting to unrestricted during startup. Consequently, the accelerated startup script fails to deliver significant improvements in boot time. Furthermore,it was observed that the accelerated startup script did not yield substantial improvements in boot time in OCP 4.12. Therefore, it might be necessary to explore alternative approaches instead of relying solely on setting CPU affinities to unrestricted cores. This update addresses the issue by removing the MC that contains the accelerated startup script and services. Moving forward, once the OCPBUGS-15102 is resolved, a unified accelerated startup method will be developed to cater to all cluster topologies. Signed-off-by: Tao Liu <tali@redhat.com>
|
/retest |
|
/jira refresh |
|
@imiller0: This pull request references Jira Issue OCPBUGS-13634, which is invalid:
Comment In 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 kubernetes/test-infra repository. |
|
/jira refresh |
openshift-ci-robot
added
jira/valid-bug
|
@imiller0: This pull request references Jira Issue OCPBUGS-13634, which is valid. 3 validation(s) were run on this bug
Requesting review from QA contact: In 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 kubernetes/test-infra repository. |
|
@openshift-ci-robot: GitHub didn't allow me to request PR reviews from the following users: mpmaruthu. Note that only openshift-kni members and repo collaborators can review this PR, and authors cannot review their own PRs. In 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 kubernetes/test-infra repository. |
|
/retest |
|
/test images |
1 similar comment
|
/test images |
|
@tliu2021: Jira Issue OCPBUGS-13634: All pull requests linked via external trackers have merged: Jira Issue OCPBUGS-13634 has been moved to the MODIFIED state. In 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 kubernetes/test-infra repository. |
A known issue, tracked by OCPBUGS-15102 in OCP 4.13 and 4.14, could lead to the CPU affinities not resetting to unrestricted during startup. Consequently, the accelerated startup script fails to deliver significant improvements in boot time.
Furthermore, it was observed that the accelerated startup script did not yield substantial improvements in boot time in OCP 4.12. Therefore, it might be necessary to explore alternative approaches instead of relying solely on setting CPU affinities to unrestricted cores.
This update addresses the issue by removing the MC that contains the accelerated startup script and services. Moving forward, once the OCPBUGS-15102 is resolved, a unified accelerated startup method will be developed to cater to all cluster topologies.