Update nvme /dev/ device search path to only identify drive/namespace paths#1485
Conversation
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: pwschuurman The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/assign @amacaskill |
|
/lgtm |
|
/cherrypick release-1.12 |
|
/cherrypick release-1.11 |
|
@pwschuurman: #1485 failed to apply on top of branch "release-1.12": 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 kubernetes/test-infra repository. |
|
@pwschuurman: #1485 failed to apply on top of branch "release-1.11": 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 kubernetes/test-infra repository. |
…485-upstream-release-1.11 [release-1.11] Automated cherry pick of #1485: Update nvme /dev/ device search path to only identify
…485-upstream-release-1.12 [release-1.12] Automated cherry pick of #1485: Update nvme /dev/ device search path to only identify
…485-upstream-release-1.10 [release-1.10] Automated cherry pick of #1485: Update nvme /dev/ device search path to only identify
…485-upstream-release-1.8 [release-1.8] Automated cherry pick of #1485: Update nvme /dev/ device search path to only identify
…485-upstream-release-1.9 [release-1.9] Automated cherry pick of #1485: Update nvme /dev/ device search path to only identify
What type of PR is this?
/kind bug
What this PR does / why we need it:
The current code that finds NVMe device paths looks for
/dev/nvme*, which returns partition and device paths. The mount code is only concerned about drive/namespace paths, so the found paths should be restricted to these.Which issue(s) this PR fixes:
Fixes #1480
Special notes for your reviewer:
Does this PR introduce a user-facing change?: