-
Notifications
You must be signed in to change notification settings - Fork 9.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
9775 launch config with instance store #9810
9775 launch config with instance store #9810
Conversation
* this revers part of commit 3d330bd, re-enabling the ability to use instance-store volumes * fetchRootDeviceName() will again return `nil, nil` when used against instance-store AMIs * re-add the `nil` value checking to fetchRootDeviceName() usage in readBlockDeviceMappingsFromConfig()
* added instance store data AMI source * added basic acceptance test using this instance-store AMI
Ended up having to extract a list of tests, and then run them each individually. Several tests were re-run due to low availability of m1 instances in us-west-2; perhaps more of these should be moved to
|
Thank you for your work! Any chance to get some traction on this? This is something that we have run into more than once. I would love to get a proper fix in instead of having to do workarounds. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me, thank you so much for this fix and associated testing, @jc-asdf 🚀
New test prior to fix:
--- FAIL: TestAccAWSLaunchConfiguration_withInstanceStoreAMI (13.84s)
testing.go:640: Step 0 error: errors during apply:
Error: Instance store backed AMIs do not provide a root device name - Use an EBS AMI
Output from acceptance testing:
--- PASS: TestAccAWSLaunchConfiguration_withSpotPrice (19.05s)
--- PASS: TestAccAWSLaunchConfiguration_withInstanceStoreAMI (20.40s)
--- PASS: TestAccAWSLaunchConfiguration_withBlockDevices (20.90s)
--- PASS: TestAccAWSLaunchConfiguration_withEncryption (21.66s)
--- PASS: TestAccAWSLaunchConfiguration_ebs_noDevice (21.67s)
--- PASS: TestAccAWSLaunchConfiguration_withIAMProfile (29.41s)
--- PASS: TestAccAWSLaunchConfiguration_encryptedRootBlockDevice (34.32s)
--- PASS: TestAccAWSLaunchConfiguration_basic (35.35s)
--- PASS: TestAccAWSLaunchConfiguration_userData (37.26s)
--- PASS: TestAccAWSLaunchConfiguration_updateEbsBlockDevices (37.48s)
--- PASS: TestAccAWSLaunchConfiguration_updateRootBlockDevice (39.25s)
--- PASS: TestAccAWSLaunchConfiguration_withVpcClassicLink (39.58s)
This has been released in version 2.49.0 of the Terraform AWS provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template for triage. Thanks! |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks! |
Community Note
Closes #9775
Release note for CHANGELOG:
Output from acceptance testing:
Two sections affected.
aws_launch_configuration
:The
aws_instance
tests are odd - no matter what I try, it keeps trying to make some of the test resources inus-east-1
, which is not where the test AMIs are located. I've set and exportedAWS_DEFAULT_REGION=us-west-2
, and set the region in the default aws configuration, etc... but no luck.I suspect I'm running into some variation of what's described in #8316 when running the
aws_instance
tests. Running individually is working so far. Will attach a full list of the individual tests run.