Support updated GPU AMI naming convention #532
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
The new GPU AMIs(Feb. 11) are named with timestamp value, not “v{YYYYMMDD}” format
3 tasks
errordeveloper
approved these changes
Feb 12, 2019
|
Thanks a lot, well spotted! |
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.
Description
It seems that the new GPU AMIs naming convention has been changed by AWS side. They're named with timestamp value instead of “v{YYYYMMDD}” format.
This PR fixes the problem that the AMI resolver cannot find the new GPU AMIs due to the change above.
Checklist
make build)make test)make integration-test)humans.txtfile