Skip to content
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

Merged

Conversation

jsafrane
Copy link

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

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.
Copy link

openshift-ci bot commented Apr 26, 2024

[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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 26, 2024
@jsafrane
Copy link
Author

/jira cherrypick OCPBUGS-23260

@jsafrane jsafrane changed the title UPSTREAM: 1919: Add reserved-volume-attachments OCPBUGS-23260: UPSTREAM: 1919: Add reserved-volume-attachments Apr 26, 2024
@jsafrane jsafrane changed the title OCPBUGS-23260: UPSTREAM: 1919: Add reserved-volume-attachments [release-4.15] OCPBUGS-23260: UPSTREAM: 1919: Add reserved-volume-attachments Apr 26, 2024
@bertinatto
Copy link
Member

/lgtm
/backport-risk-assessed

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Apr 26, 2024
@bertinatto
Copy link
Member

/label backport-risk-assessed

@openshift-ci openshift-ci bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Apr 26, 2024
@jsafrane
Copy link
Author

/hold
I need to clone the bug manually

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Apr 26, 2024
@jsafrane jsafrane changed the title [release-4.15] OCPBUGS-23260: UPSTREAM: 1919: Add reserved-volume-attachments [release-4.15] OCPBUGS-33043: UPSTREAM: 1919: Add reserved-volume-attachments Apr 26, 2024
@openshift-ci-robot openshift-ci-robot added jira/severity-critical Referenced Jira bug's severity is critical for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Apr 26, 2024
@openshift-ci-robot
Copy link

@jsafrane: This pull request references Jira Issue OCPBUGS-33043, which is invalid:

  • expected the bug to target either version "4.15." or "openshift-4.15.", but it targets "4.16.0" instead
  • release note text must be set and not match the template OR release note type must be set to "Release Note Not Required"
  • expected Jira Issue OCPBUGS-33043 to depend on a bug targeting a version in 4.16.0 and 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:

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

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.

@jsafrane
Copy link
Author

/jira refresh

@openshift-ci-robot
Copy link

@jsafrane: This pull request references Jira Issue OCPBUGS-33043, which is invalid:

  • release note text must be set and not match the template OR release note type must be set to "Release Note Not Required"
  • expected Jira Issue OCPBUGS-33043 to depend on a bug targeting a version in 4.16.0 and 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.

In response to this:

/jira refresh

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.

@jsafrane
Copy link
Author

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Apr 26, 2024
@openshift-ci-robot
Copy link

@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
  • bug is open, matching expected state (open)
  • bug target version (4.15.z) matches configured target version for branch (4.15.z)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note type set to "Release Note Not Required"
  • dependent bug Jira Issue OCPBUGS-23260 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-23260 targets the "4.16.0" version, which is one of the valid target versions: 4.16.0
  • bug has dependents

Requesting review from QA contact:
/cc @Phaow

In response to this:

/jira refresh

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 openshift-ci bot requested a review from Phaow April 26, 2024 13:51
@jsafrane
Copy link
Author

/hold cancel

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Apr 26, 2024
@Phaow
Copy link

Phaow commented Apr 28, 2024

/label cherry-pick-approved
/label qe-approved

Pre verify passed on 4.15.0-0.test-2024-04-28-023909-ci-ln-b5jxff2-latest

Firstly I checked the --reserved-volume-attachments=1 arg already added to csi-node ds in the fix build.

$ 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.

@openshift-ci openshift-ci bot added cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. qe-approved Signifies that QE has signed off on this PR labels Apr 28, 2024
@openshift-ci-robot
Copy link

@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
  • bug is open, matching expected state (open)
  • bug target version (4.15.z) matches configured target version for branch (4.15.z)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note type set to "Release Note Not Required"
  • dependent bug Jira Issue OCPBUGS-23260 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-23260 targets the "4.16.0" version, which is one of the valid target versions: 4.16.0
  • bug has dependents

Requesting review from QA contact:
/cc @Phaow

In response to this:

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

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.

@Phaow
Copy link

Phaow commented Apr 28, 2024

/test e2e-aws-ovn-upgrade

Copy link

openshift-ci bot commented Apr 28, 2024

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

@openshift-merge-bot openshift-merge-bot bot merged commit 7043c1c into openshift:release-4.15 Apr 28, 2024
9 checks passed
@openshift-ci-robot
Copy link

@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 refresh.

Jira Issue OCPBUGS-33043 has not been moved to the MODIFIED state.

In response to this:

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

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-bot
Copy link

[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.
All builds following this will include this PR.

@jsafrane
Copy link
Author

/cherry-pick release-4.14

@openshift-cherrypick-robot

@jsafrane: #263 failed to apply on top of branch "release-4.14":

Applying: UPSTREAM: 1919: Add reserved-volume-attachments
Using index info to reconstruct a base tree...
M	cmd/main.go
M	cmd/options.go
M	cmd/options_test.go
M	pkg/driver/driver.go
M	pkg/driver/driver_test.go
M	pkg/driver/node.go
M	pkg/driver/node_test.go
Falling back to patching base and 3-way merge...
Auto-merging pkg/driver/node_test.go
CONFLICT (content): Merge conflict in pkg/driver/node_test.go
Auto-merging pkg/driver/node.go
CONFLICT (content): Merge conflict in pkg/driver/node.go
Auto-merging pkg/driver/driver_test.go
Auto-merging pkg/driver/driver.go
CONFLICT (content): Merge conflict in pkg/driver/driver.go
Auto-merging cmd/options_test.go
CONFLICT (content): Merge conflict in cmd/options_test.go
Auto-merging cmd/options.go
Auto-merging cmd/main.go
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 UPSTREAM: 1919: Add reserved-volume-attachments
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to this:

/cherry-pick release-4.14

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-merge-robot
Copy link

Fix included in accepted release 4.15.0-0.nightly-2024-04-29-094148

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. jira/severity-critical Referenced Jira bug's severity is critical for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. qe-approved Signifies that QE has signed off on this PR
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet