-
Notifications
You must be signed in to change notification settings - Fork 20
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.
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
[release-4.15] OCPBUGS-33043: UPSTREAM: 1919: Add reserved-volume-attachments #263
[release-4.15] OCPBUGS-33043: UPSTREAM: 1919: Add reserved-volume-attachments #263
Conversation
Pick both commits in kubernetes-sigs#1919 to OCP. Introduce --reserved-volume-attachments cmd line option that disables loading list of volume attachments from instance metadata. Instance metadata has volume attachments that were present on instance boot, which may be different than the current nr. of attachments. In addition, it may include CSI volumes that were not drained before reboot, and thus the value may be completely wrong. --reserved-volume-attachments simply reserves given nr. of attachments for any system disks. Typically it should be 1 for the root volume.
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jsafrane 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 |
/jira cherrypick OCPBUGS-23260 |
/lgtm |
/label backport-risk-assessed |
/hold |
@jsafrane: This pull request references Jira Issue OCPBUGS-33043, 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 openshift-eng/jira-lifecycle-plugin repository. |
/jira refresh |
@jsafrane: This pull request references Jira Issue OCPBUGS-33043, 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 openshift-eng/jira-lifecycle-plugin repository. |
/jira refresh |
@jsafrane: This pull request references Jira Issue OCPBUGS-33043, which is valid. The bug has been moved to the POST state. 7 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 openshift-eng/jira-lifecycle-plugin repository. |
/hold cancel |
/label cherry-pick-approved Pre verify passed on Firstly I checked the $ oc -n openshift-cluster-csi-drivers get ds/aws-ebs-csi-driver-node -oyaml| grep 'reserved'
- --reserved-volume-attachments=1 The presubmit CI all looks good regression test passed. In addition, I tested with fresh installed pre merge build cluster with m5.8xlarge instance type(csinode allocatable volumes count: "26"), create statefulset with pvc 20 replicas use nodeAffinity to make the pod schedule to specified node and reboot the node several times, then create statefulset with pvc 6 replicas use nodeAffinity to make the pod schedule to specified node, the sts all replicas become ready. |
@jsafrane: This pull request references Jira Issue OCPBUGS-33043, which is valid. The bug has been moved to the POST state. 7 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 openshift-eng/jira-lifecycle-plugin repository. |
/test e2e-aws-ovn-upgrade |
@jsafrane: 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/test-infra repository. I understand the commands that are listed here. |
7043c1c
into
openshift:release-4.15
@jsafrane: Jira Issue OCPBUGS-33043: Some pull requests linked via external trackers have merged: The following pull requests linked via external trackers have not merged:
These pull request must merge or be unlinked from the Jira bug in order for it to move to the next state. Once unlinked, request a bug refresh with Jira Issue OCPBUGS-33043 has not 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 openshift-eng/jira-lifecycle-plugin repository. |
[ART PR BUILD NOTIFIER] This PR has been included in build ose-aws-ebs-csi-driver-container-v4.15.0-202404281138.p0.g7043c1c.assembly.stream.el9 for distgit ose-aws-ebs-csi-driver. |
/cherry-pick release-4.14 |
@jsafrane: #263 failed to apply on top of branch "release-4.14":
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. |
Fix included in accepted release 4.15.0-0.nightly-2024-04-29-094148 |
Pick both commits from kubernetes-sigs#1919 to OCP.
Introduce
--reserved-volume-attachments
cmd line option that disables loading list of volume attachments from instance metadata.Instance metadata has volume attachments that were present on instance boot, which may be different than the current nr. of attachments. In addition, it may include CSI volumes that were not drained before reboot, and thus the value may be completely wrong.
--reserved-volume-attachments
simply reserves given nr. of attachments for any system disks. Typically it should be 1 for the root volume.cc @openshift/storage