-
Notifications
You must be signed in to change notification settings - Fork 9.2k
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
aws_launch_template - panic: interface conversion: interface {} is nil, not map[string]interface {} #7885
Comments
After looking through the panic error stack and the terraform provider code I removed the spot_options section from the terraform
var.spot_price was set to "". Reading through the aws provider code this should not be an issue
The error has not happened since removing that section |
Relevant part of log
|
Hi @JPScutt thanks for reporting this issue and for detailing your workaround. Looks like we might need a nil check or two in place. |
Hi @JPScutt - any chance you'd be able to test this using the most recent version of the AWS provider? I've so far been unable to reproduce this on 2.11.0 or 2.10.0, but if you're still seeing it on those versions that will be a good data point for us to start digging into more. Thanks! |
Hey @JPScutt - I was just able to reproduce this crash on 2.11.0 so probably no need to test on your end if you haven't already - I'll continue looking into this now. Thanks! |
Okay, it was on the list to look at today so saved me a job.
Thanks
…On Mon, May 20, 2019 at 12:38 PM Ryn Daniels ***@***.***> wrote:
Hey @JPScutt <https://github.com/JPScutt> - I was just able to reproduce
this crash on 2.11.0 so probably no need to test on your end if you haven't
already - I'll continue looking into this now. Thanks!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#7885>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AHXFILLOFY4YFXCYKBHT3FDPWKEOFANCNFSM4G5BNUNA>
.
--
*Jonathan Scutt *Platform Engineer
Direct: +44 (0)1285 853235
jonathan.scutt@iress.co.uk
Office: +44 (0)345 068 1000
Jessop House, Jessop Avenue
Cheltenham, GL50 3SH
www.iress.com
[image: Twitter] <https://twitter.com/iressUK>
[image: Youtube] <https://www.youtube.com/channel/UCXXYqZvVHp0rqKYh9pJ9fbQ>
[image: Linkedin] <https://www.linkedin.com/company/iress/>
--
**********************************************************************************************
Important Note
This email (including any attachments) contains information
which is confidential and may be subject to legal privilege. If you are
not the intended recipient you must not use, distribute or copy this email.
If you have received this email in error please notify the
sender
immediately and delete this email. Any views expressed in this email are
not necessarily the views of IRESS Limited.
It is the duty of the
recipient to virus scan and otherwise test the information provided before
loading onto any computer system.
IRESS Limited does not warrant that the
information is free of a virus or any other defect or error.
**********************************************************************************************
|
This has been released in version 2.14.0 of the Terraform AWS provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. |
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
Terraform Version
Terraform v0.11.11
provider.aws v2.1.0
Affected Resource(s)
aws_launch_template
aws_security_group
Terraform Configuration Files
Debug Output
Expected Behavior
The new auto scaling instances would successfully be created
Actual Behavior
panic
Steps to Reproduce
Issue is intermittent, 1 in 4 CI builds are successfully (with no changes made)
References
I couldn't find any.
The text was updated successfully, but these errors were encountered: