This repository has been archived by the owner on Jan 11, 2023. It is now read-only.
fix disk unavailable issue when mounting multiple azure disks due to dev name change #2410
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What this PR does / why we need it:
fix disk unavailable issue when mounting multiple azure disks due to dev name change
When User mount the 6th azure data disk on an D2_V2 VM, other azure disk would be unavailable due to device name change. This PR set the default
cachingmode
asNone
to fix this issue.You could find more details in this upstream PR: kubernetes/kubernetes#60346
Which issue this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close that issue when PR gets merged): fixes #1918Special notes for your reviewer:
@jackfrancis @JiangtianLi This is a critical bug fix, we have changed the default
cachingmode
value asNone
in upstream code, while as a simple workaround, we could change thecachingmode
value toNone
in azure disk storage class. Could you fix it in AKS also? Thanks.Release note: