-
Notifications
You must be signed in to change notification settings - Fork 38
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
chore(bors): merge pull request #695
695: Fixup correct nvme controller and make child add v1 idempotent r=tiagolobocastro a=tiagolobocastro feat(csi/node/timeout): add nvme-io-engine timeout and parse humantime Adds new parameter "--nvme-io-timeout". This is used to set the timeout per nvme block device. TODO: Check if this is enough to avoid setting the global timeout.. Also let's parse the "--nvme-core-io-timeout" as humantime as well.. Signed-off-by: Tiago Castro <tiagolobocastro@gmail.com> --- fix(nexus/add-child/v1): make add child v1 idempotent When v1 nexus add child was added, it was not made idempotent. Even though this is not an issue per se, as the child eventually gets GCd and re-added it can cause strange logging.. TODO: should we have different behaviour depending on the state? Example if faulted should we remove/readd? Bonus: Fixes old test which stopped working a long time ago when pstor was enabled for the data-plane by not enabling it for that particular test only.. Signed-off-by: Tiago Castro <tiagolobocastro@gmail.com> --- fix(csi-node/nvmf/fixup): fixup correct nvme controller When we replace an existing path, the new path has a different controller number. And so the controller number and device number now mismatch, meaning we can not safely deref /sys/class/nvme/nvme{major} Instead, we can simply deref /sys/class/block/nvme{major}c*n1/queue The major ensures we use the original device number, and the glob ensures we modify the timeout for all controllers. Signed-off-by: Tiago Castro <tiagolobocastro@gmail.com> Co-authored-by: Tiago Castro <tiagolobocastro@gmail.com>
- Loading branch information
Showing
10 changed files
with
207 additions
and
76 deletions.
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
This file contains 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
Oops, something went wrong.