Fixed custom storage for AMIs #5625
Merged
Conversation
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
teddytpc1
approved these changes
Jul 30, 2024
juliamagan
approved these changes
Jul 31, 2024
juliamagan
deleted the
bug/5617-the-allocator-module-fails-to-allocate-instances-in-aws-due-to-volume-size
branch
This was referenced Aug 2, 2024
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
close #5617
Description
The method for obtaining the storage required by the AMI is updated, and with this we validate what the ideal value is for each AMI.
Testing performed
Debian 12 amd: #5617 (comment)
Debian 12 arm: #5617 (comment)
Oracle Linux 9: #5617 (comment)
Windows 10: #5617 (comment)
macOS Sonoma: #5617 (comment)