IAmStoxe/oracle-free-tier-wirehole

null_resource.cloud_init_watcher_provisioner (remote-exec) never finishes

itskvad opened this issue · 1 comments

Terraform v1.0.5
on windows_amd64

  • provider registry.terraform.io/hashicorp/null v3.1.0
  • provider registry.terraform.io/hashicorp/oci v4.40.0

null_resource.cloud_init_watcher_provisioner (remote-exec): Connected! null_resource.cloud_init_watcher_provisioner (remote-exec): wireguard | [services.d] done. null_resource.cloud_init_watcher_provisioner (remote-exec): wireguard | [#] ip link add wg0 type wireguard null_resource.cloud_init_watcher_provisioner (remote-exec): wireguard | [#] wg setconf wg0 /dev/fd/63 null_resource.cloud_init_watcher_provisioner (remote-exec): wireguard | [#] ip -4 address add 10.6.0.1 dev wg0 null_resource.cloud_init_watcher_provisioner (remote-exec): wireguard | [#] ip link set mtu 1420 up dev wg0 null_resource.cloud_init_watcher_provisioner (remote-exec): wireguard | [#] ip -4 route add 10.6.0.2/32 dev wg0 null_resource.cloud_init_watcher_provisioner (remote-exec): wireguard | [#] iptables -A FORWARD -i wg0 -j ACCEPT; iptables -A FORWARD -o wg0 -j ACCEPT; iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE null_resource.cloud_init_watcher_provisioner (remote-exec): wireguard | .:53 null_resource.cloud_init_watcher_provisioner (remote-exec): wireguard | CoreDNS-1.8.4 null_resource.cloud_init_watcher_provisioner (remote-exec): wireguard | linux/amd64, go1.16.4, 053c4d5 null_resource.cloud_init_watcher_provisioner: Still creating... [10s elapsed] null_resource.cloud_init_watcher_provisioner: Still creating... [20s elapsed] null_resource.cloud_init_watcher_provisioner: Still creating... [30s elapsed] null_resource.cloud_init_watcher_provisioner: Still creating... [40s elapsed] null_resource.cloud_init_watcher_provisioner: Still creating... [50s elapsed] null_resource.cloud_init_watcher_provisioner: Still creating... [1m0s elapsed]

Cancelling out is fine.
Wireguard deployment works. The above never finishes so TF thinks the state is tainted.

`
Terraform used the selected providers to generate the following execution plan. Resource actions are indicated with the following symbols:
-/+ destroy and then create replacement

Terraform will perform the following actions:

null_resource.cloud_init_watcher_provisioner is tainted, so must be replaced

-/+ resource "null_resource" "cloud_init_watcher_provisioner" {
~ id = "4704460804359287746" -> (known after apply)
# (1 unchanged attribute hidden)
}`

Faced with it too.
Ubuntu 20.04
Terraform 1.1.1