Fix Azure compute driver to allow adding maximum number of disks when LUN is unspecified #1372
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.
Fix Azure compute driver to allow adding maximum number of disks when LUN is unspecified
Description
When the LUN is unspecified in the
attach_volume
method, it finds the lowest available number to attach the volume to. The maximum number of data disks on an Azure VM is 64, which means LUNs can range from 0 to 63.The current logic to figure out the LUN iterates from 0 to 62:
for lun in range(0, 63)
. When you try to add the Nth device where N = maximum number of data disks allowed for that instance size, this code raisesLibcloudError("No LUN available to attach new disk.")
.This PR fixes this to ensure the last LUN is usable.
Status
Checklist (tick everything that applies)