热门标签 | HotTags
当前位置:  开发笔记 > 编程语言 > 正文

TerraformCrashduringTerraformapply

Thisissuewasoriginallyopenedbyashashicorp/terraform#20180.Itwasmigratedh

This issue was originally opened by as hashicorp/terraform#20180. It was migrated here as a result of the provider split. The original body of the issue is below.

Terraform Version

Terraform v0.11.11
+ provider.aws v1.57.0

Terraform Configuration Files

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
hcl

resource "aws_s3_bucket" "bucket" {

  bucket = "bucket"

  acl    = "private"

  cors_rule {

    allowed_headers = ["*"]

    allowed_methods = ["GET", "HEAD"]

    allowed_origins = ["*"]

    max_age_seconds = 86400

  }

  logging {

    target_bucket = "target-bucket"

    target_prefix = "s3-logs/"

  }

   website {

    index_document = "index.html"

  }



  replication_configuration {

    role = "${module.bucket-replication.replication-role-arn}"

    rules {

      destination {

        bucket = "${module.bucket-replication.bucket-dr-arn}"

        replica_kms_key_id = "${data.aws_kms_key.east-s3.arn}"

      }



      id = "replication-role-for-bucket"

      priority = 1

      source_selection_criteria {

        sse_kms_encrypted_objects {

          enabled = true

        }

      }



      status = "Enabled"



    }

  }



}


Debug Output


Crash Output

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
hcl

2019/01/31 17:48:32 [INFO] Terraform version: 0.11.11  

2019/01/31 17:48:32 [INFO] Go runtime version: go1.11.4

2019/01/31 17:48:32 [INFO] CLI args: []string{"/usr/local/Cellar/terraform/0.11.11/bin/terraform", "apply"}

2019/01/31 17:48:32 [DEBUG] Attempting to open CLI config file: /Users/lizhifan/.terraformrc

2019/01/31 17:48:32 [DEBUG] File doesn't exist, but doesn't need to. Ignoring.

2019/01/31 17:48:32 [INFO] CLI command args: []string{"apply"}



2019/01/31 17:48:32 [INFO] command: empty terraform config, returning nil

2019/01/31 17:48:32 [TRACE] Preserving existing state lineage "ebdf2718-a158-36a6-9c63-dce214ec779d"

2019/01/31 17:48:32 [TRACE] Preserving existing state lineage "ebdf2718-a158-36a6-9c63-dce214ec779d"

2019/01/31 17:48:32 [INFO] command: backend initialized:

2019/01/31 17:48:32 [DEBUG] checking for provider in "."

2019/01/31 17:48:32 [DEBUG] checking for provider in "/usr/local/Cellar/terraform/0.11.11/bin"

2019/01/31 17:48:32 [DEBUG] checking for provider in ".terraform/plugins/darwin_amd64"

2019/01/31 17:48:32 [DEBUG] found provider "terraform-provider-aws_v1.57.0_x4"

2019/01/31 17:48:32 [DEBUG] found valid plugin: "aws", "1.57.0",

...

2019/01/31 17:48:33 [TRACE] Graph after step *terraform.ConfigTransformer:



aws_s3_bucket.bucket - *terraform.NodeAbstractResource



Expected Behavior

1
2
3
4
5
6
7
8
9
10
11
Terraform will perform the following actions:



  ~ aws_s3_bucket.bucket

      acl:           "" => "private"

      force_destroy: "" => "false"



  ~ module.bucket-replication.aws_s3_bucket.bucket-dr

      acl:           "" => "private"

      force_destroy: "" => "false"



Plan: 0 to add, 2 to change, 0 to destroy.


Actual Behavior

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
panic: interface conversion: interface {} is nil, not map[string]interface {}

2019-02-01T10:45:18.800-0800 [DEBUG] plugin.terraform-provider-aws_v1.57.0_x4:

2019-02-01T10:45:18.800-0800 [DEBUG] plugin.terraform-provider-aws_v1.57.0_x4: goroutine 5945 [running]:

2019-02-01T10:45:18.800-0800 [DEBUG] plugin.terraform-provider-aws_v1.57.0_x4: github.com/terraform-providers/terraform-provider-aws/aws.resourceAwsS3BucketReplicationConfigurationUpdate(0xc00114a5b8, 0xc0007f9960, 0x19, 0x1)

2019-02-01T10:45:18.801-0800 [DEBUG] plugin.terraform-provider-aws_v1.57.0_x4:  /opt/teamcity-agent/work/5d79fe75d4460a2f/src/github.com/terraform-providers/terraform-provider-aws/aws/resource_aws_s3_bucket.go:1934 +0x1b7d

2019-02-01T10:45:18.801-0800 [DEBUG] plugin.terraform-provider-aws_v1.57.0_x4: github.com/terraform-providers/terraform-provider-aws/aws.resourceAwsS3BucketUpdate(0xc0007f9960, 0x3e87de0, 0xc0007af000, 0x24, 0x7a22080)

2019-02-01T10:45:18.801-0800 [DEBUG] plugin.terraform-provider-aws_v1.57.0_x4:  /opt/teamcity-agent/work/5d79fe75d4460a2f/src/github.com/terraform-providers/terraform-provider-aws/aws/resource_aws_s3_bucket.go:731 +0x524

2019-02-01T10:45:18.801-0800 [DEBUG] plugin.terraform-provider-aws_v1.57.0_x4: github.com/terraform-providers/terraform-provider-aws/vendor/github.com/hashicorp/terraform/helper/schema.(*Resource).Apply(0xc0012f9dc0, 0xc001310a00, 0xc0006436a0, 0x3e87de0, 0xc0007af000, 0x100b601, 0xc000089b80, 0x10bdabc)

2019-02-01T10:45:18.801-0800 [DEBUG] plugin.terraform-provider-aws_v1.57.0_x4:  /opt/teamcity-agent/work/5d79fe75d4460a2f/src/github.com/terraform-providers/terraform-provider-aws/vendor/github.com/hashicorp/terraform/helper/schema/resource.go:231 +0x250

2019-02-01T10:45:18.801-0800 [DEBUG] plugin.terraform-provider-aws_v1.57.0_x4: github.com/terraform-providers/terraform-provider-aws/vendor/github.com/hashicorp/terraform/helper/schema.(*Provider).Apply(0xc000df7d50, 0xc0013109b0, 0xc001310a00, 0xc0006436a0, 0xc000075800, 0x18, 0x9099d80)

2019-02-01T10:45:18.801-0800 [DEBUG] plugin.terraform-provider-aws_v1.57.0_x4:  /opt/teamcity-agent/work/5d79fe75d4460a2f/src/github.com/terraform-providers/terraform-provider-aws/vendor/github.com/hashicorp/terraform/helper/schema/provider.go:283 +0x9c

2019-02-01T10:45:18.801-0800 [DEBUG] plugin.terraform-provider-aws_v1.57.0_x4: github.com/terraform-providers/terraform-provider-aws/vendor/github.com/hashicorp/terraform/plugin.(*ResourceProviderServer).Apply(0xc000640e80, 0xc000643240, 0xc000655350, 0x0, 0x0)

2019-02-01T10:45:18.801-0800 [DEBUG] plugin.terraform-provider-aws_v1.57.0_x4:  /opt/teamcity-agent/work/5d79fe75d4460a2f/src/github.com/terraform-providers/terraform-provider-aws/vendor/github.com/hashicorp/terraform/plugin/resource_provider.go:527 +0x57

2019-02-01T10:45:18.801-0800 [DEBUG] plugin.terraform-provider-aws_v1.57.0_x4: reflect.Value.call(0xc0001566c0, 0xc00114bac0, 0x13, 0x45329c7, 0x4, 0xc000089f18, 0x3, 0x3, 0xc00013a100, 0xc0003b3400, ...)

2019-02-01T10:45:18.801-0800 [DEBUG] plugin.terraform-provider-aws_v1.57.0_x4:  /opt/goenv/versions/1.11.4/src/reflect/value.go:447 +0x454

2019-02-01T10:45:18.801-0800 [DEBUG] plugin.terraform-provider-aws_v1.57.0_x4: reflect.Value.Call(0xc0001566c0, 0xc00114bac0, 0x13, 0xc0005a6f18, 0x3, 0x3, 0x1b, 0x0, 0xc000a4b640)

2019-02-01T10:45:18.801-0800 [DEBUG] plugin.terraform-provider-aws_v1.57.0_x4:  /opt/goenv/versions/1.11.4/src/reflect/value.go:308 +0xa4

2019-02-01T10:45:18.801-0800 [DEBUG] plugin.terraform-provider-aws_v1.57.0_x4: net/rpc.(*service).call(0xc001209ac0, 0xc000536d20, 0xc0006be2e8, 0xc0006be300, 0xc000f15500, 0xc000641740, 0x384f440, 0xc000643240, 0x16, 0x384f480, ...)

2019-02-01T10:45:18.801-0800 [DEBUG] plugin.terraform-provider-aws_v1.57.0_x4:  /opt/goenv/versions/1.11.4/src/net/rpc/server.go:384 +0x14e

2019-02-01T10:45:18.801-0800 [DEBUG] plugin.terraform-provider-aws_v1.57.0_x4: created by net/rpc.(*Server).ServeCodec

2019-02-01T10:45:18.801-0800 [DEBUG] plugin.terraform-provider-aws_v1.57.0_x4:  /opt/goenv/versions/1.11.4/src/net/rpc/server.go:481 +0x47e

2019/02/01 10:45:18 [TRACE] root: eval: *terraform.EvalWriteState

2019/02/01 10:45:18 [TRACE] root: eval: *terraform.EvalApplyProvisioners

2019/02/01 10:45:18 [TRACE] root: eval: *terraform.EvalIf

2019/02/01 10:45:18 [TRACE] root: eval: *terraform.EvalWriteState

2019/02/01 10:45:18 [TRACE] root: eval: *terraform.EvalWriteDiff

2019/02/01 10:45:18 [TRACE] root: eval: *terraform.EvalApplyPost

2019/02/01 10:45:18 [ERROR] root: eval: *terraform.EvalApplyPost, err: 1 error(s) occurred:



* aws_s3_bucket.figma-alpha-api: unexpected EOF

2019/02/01 10:45:18 [ERROR] root: eval: *terraform.EvalSequence, err: 1 error(s) occurred:



* aws_s3_bucket.figma-alpha-api: unexpected EOF

2019/02/01 10:45:18 [TRACE] [walkApply] Exiting eval tree: aws_s3_bucket.figma-alpha-api

2019/02/01 10:45:18 [TRACE] dag/walk: upstream errored, not walking "provider.aws (close)"

2019/02/01 10:45:18 [TRACE] dag/walk: upstream errored, not walking "meta.count-boundary (count boundary fixup)"

2019/02/01 10:45:18 [TRACE] dag/walk: upstream errored, not walking "root"

2019-02-01T10:45:18.805-0800 [DEBUG] plugin: plugin process exited: path=/Users/lizhifan/figma/figma/config/terraform/prod/us-west-2/.terraform/plugins/darwin_amd64/terraform-provider-aws_v1.57.0_x4

2019/02/01 10:45:18 [TRACE] Preserving existing state lineage "bbb9ed33-3d8a-fd69-6079-acdd2e010423"

2019/02/01 10:45:18 [TRACE] Preserving existing state lineage "bbb9ed33-3d8a-fd69-6079-acdd2e010423"

2019/02/01 10:45:18 [TRACE] Preserving existing state lineage "bbb9ed33-3d8a-fd69-6079-acdd2e010423"

2019/02/01 10:45:18 [TRACE] Preserving existing state lineage "bbb9ed33-3d8a-fd69-6079-acdd2e010423"

2019/02/01 10:45:18 [DEBUG] plugin: waiting for all plugin processes to complete...

2019-02-01T10:45:18.860-0800 [WARN ] plugin: error closing client during Kill: err="connection is shut down"







!!!!!!!!!!!!!!!!!!!!!!!!!!! TERRAFORM CRASH !!!!!!!!!!!!!!!!!!!!!!!!!!!!

该提问来源于开源项目:hashicorp/terraform-provider-aws

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!


   



推荐阅读
  • Android系统源码分析Zygote和SystemServer启动过程详解
    本文详细解析了Android系统源码中Zygote和SystemServer的启动过程。首先介绍了系统framework层启动的内容,帮助理解四大组件的启动和管理过程。接着介绍了AMS、PMS等系统服务的作用和调用方式。然后详细分析了Zygote的启动过程,解释了Zygote在Android启动过程中的决定作用。最后通过时序图展示了整个过程。 ... [详细]
  • 本文主要解析了Open judge C16H问题中涉及到的Magical Balls的快速幂和逆元算法,并给出了问题的解析和解决方法。详细介绍了问题的背景和规则,并给出了相应的算法解析和实现步骤。通过本文的解析,读者可以更好地理解和解决Open judge C16H问题中的Magical Balls部分。 ... [详细]
  • 如何自行分析定位SAP BSP错误
    The“BSPtag”Imentionedintheblogtitlemeansforexamplethetagchtmlb:configCelleratorbelowwhichi ... [详细]
  • IhaveconfiguredanactionforaremotenotificationwhenitarrivestomyiOsapp.Iwanttwodiff ... [详细]
  • CSS3选择器的使用方法详解,提高Web开发效率和精准度
    本文详细介绍了CSS3新增的选择器方法,包括属性选择器的使用。通过CSS3选择器,可以提高Web开发的效率和精准度,使得查找元素更加方便和快捷。同时,本文还对属性选择器的各种用法进行了详细解释,并给出了相应的代码示例。通过学习本文,读者可以更好地掌握CSS3选择器的使用方法,提升自己的Web开发能力。 ... [详细]
  • 知识图谱——机器大脑中的知识库
    本文介绍了知识图谱在机器大脑中的应用,以及搜索引擎在知识图谱方面的发展。以谷歌知识图谱为例,说明了知识图谱的智能化特点。通过搜索引擎用户可以获取更加智能化的答案,如搜索关键词"Marie Curie",会得到居里夫人的详细信息以及与之相关的历史人物。知识图谱的出现引起了搜索引擎行业的变革,不仅美国的微软必应,中国的百度、搜狗等搜索引擎公司也纷纷推出了自己的知识图谱。 ... [详细]
  • 本文详细介绍了在ASP.NET中获取插入记录的ID的几种方法,包括使用SCOPE_IDENTITY()和IDENT_CURRENT()函数,以及通过ExecuteReader方法执行SQL语句获取ID的步骤。同时,还提供了使用这些方法的示例代码和注意事项。对于需要获取表中最后一个插入操作所产生的ID或马上使用刚插入的新记录ID的开发者来说,本文提供了一些有用的技巧和建议。 ... [详细]
  • 在重复造轮子的情况下用ProxyServlet反向代理来减少工作量
    像不少公司内部不同团队都会自己研发自己工具产品,当各个产品逐渐成熟,到达了一定的发展瓶颈,同时每个产品都有着自己的入口,用户 ... [详细]
  • 本文介绍了一个在线急等问题解决方法,即如何统计数据库中某个字段下的所有数据,并将结果显示在文本框里。作者提到了自己是一个菜鸟,希望能够得到帮助。作者使用的是ACCESS数据库,并且给出了一个例子,希望得到的结果是560。作者还提到自己已经尝试了使用"select sum(字段2) from 表名"的语句,得到的结果是650,但不知道如何得到560。希望能够得到解决方案。 ... [详细]
  • 本文介绍了安全性要求高的真正密码随机数生成器的概念和原理。首先解释了统计学意义上的伪随机数和真随机数的区别,以及伪随机数在密码学安全中的应用。然后讨论了真随机数的定义和产生方法,并指出了实际情况下真随机数的不可预测性和复杂性。最后介绍了随机数生成器的概念和方法。 ... [详细]
  • Iamtryingtomakeaclassthatwillreadatextfileofnamesintoanarray,thenreturnthatarra ... [详细]
  • 向QTextEdit拖放文件的方法及实现步骤
    本文介绍了在使用QTextEdit时如何实现拖放文件的功能,包括相关的方法和实现步骤。通过重写dragEnterEvent和dropEvent函数,并结合QMimeData和QUrl等类,可以轻松实现向QTextEdit拖放文件的功能。详细的代码实现和说明可以参考本文提供的示例代码。 ... [详细]
  • 本文讨论了一个关于cuowu类的问题,作者在使用cuowu类时遇到了错误提示和使用AdjustmentListener的问题。文章提供了16个解决方案,并给出了两个可能导致错误的原因。 ... [详细]
  • 本文介绍了在Linux下安装Perl的步骤,并提供了一个简单的Perl程序示例。同时,还展示了运行该程序的结果。 ... [详细]
  • Java 11相对于Java 8,OptaPlanner性能提升有多大?
    本文通过基准测试比较了Java 11和Java 8对OptaPlanner的性能提升。测试结果表明,在相同的硬件环境下,Java 11相对于Java 8在垃圾回收方面表现更好,从而提升了OptaPlanner的性能。 ... [详细]
author-avatar
拍友2502882883
这个家伙很懒,什么也没留下!
PHP1.CN | 中国最专业的PHP中文社区 | DevBox开发工具箱 | json解析格式化 |PHP资讯 | PHP教程 | 数据库技术 | 服务器技术 | 前端开发技术 | PHP框架 | 开发工具 | 在线工具
Copyright © 1998 - 2020 PHP1.CN. All Rights Reserved | 京公网安备 11010802041100号 | 京ICP备19059560号-4 | PHP1.CN 第一PHP社区 版权所有