Skip to content
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

Unable to use normally #18

Open
qingfengfenga opened this issue Feb 27, 2023 · 0 comments
Open

Unable to use normally #18

qingfengfenga opened this issue Feb 27, 2023 · 0 comments

Comments

@qingfengfenga
Copy link

Refer to this document
https://devops-stack.io/docs/0.59.1/howtos/quickstart_k3s_docker.html#_deploy_the_cluster

module.cluster.module.cluster.null_resource.wait_for_cluster: Still creating... [1h50m40s elapsed]
module.cluster.module.cluster.null_resource.wait_for_cluster: Still creating... [1h50m50s elapsed]
module.cluster.module.cluster.null_resource.wait_for_cluster: Still creating... [1h51m0s elapsed]
module.cluster.module.cluster.null_resource.wait_for_cluster: Still creating... [1h51m10s elapsed]
^CStopping operation...

Interrupt received.
Please wait for Terraform to exit or data loss may occur.
Gracefully shutting down...

╷
│ Warning: Deprecated attribute
│
│   on .terraform/modules/cluster.cluster/main.tf line 3, in locals:
│    3:   cluster_endpoint = coalesce(var.cluster_endpoint, docker_container.k3s_server.ip_address)
│
│ The attribute "ip_address" is deprecated. Refer to the provider documentation for details.
│
│ (and 21 more similar warnings elsewhere)
╵
╷
│ Warning: Argument is deprecated
│
│   with module.cluster.tls_self_signed_cert.root,
│   on .terraform/modules/cluster/modules/k3s/docker/distrib-main.tf line 156, in resource "tls_self_signed_cert" "root":
│  156:   key_algorithm   = "ECDSA"
│
│ This is now ignored, as the key algorithm is inferred from the `private_key_pem`.
╵
╷
│ Error: execution halted
│
│
╵
╷
│ Error: execution halted
│
│
╵
╷
│ Error: local-exec provisioner error
│
│   with module.cluster.module.cluster.null_resource.wait_for_cluster,
│   on .terraform/modules/cluster.cluster/main.tf line 173, in resource "null_resource" "wait_for_cluster":
│  173:   provisioner "local-exec" {
│
│ Error running command 'for i in `seq 1 60`; do if `command -v wget > /dev/null`; then wget --no-check-certificate -O
│ - -q $ENDPOINT/ping >/dev/null && exit 0 || true; else curl -k -s $ENDPOINT/ping >/dev/null && exit 0 || true;fi;
│ sleep 5; done; echo TIMEOUT && exit 1': signal: interrupt. Output:
╵

Stack trace from the terraform-provider-htpasswd_v0.9.1 plugin:

panic: close of nil channel

goroutine 65 [running]:
github.com/hashicorp/terraform-plugin-go/tfprotov5/server.(*server).stop(0xc000078140)
        github.com/hashicorp/[email protected]/tfprotov5/server/server.go:201 +0x71
github.com/hashicorp/terraform-plugin-go/tfprotov5/server.(*server).Stop(0xc000078140, 0xc8ea60, 0xc000302150, 0xc0003021b0, 0xc000078140, 0xc000302150, 0xc000260ba0)
        github.com/hashicorp/[email protected]/tfprotov5/server/server.go:215 +0xa6
github.com/hashicorp/terraform-plugin-go/tfprotov5/internal/tfplugin5._Provider_Stop_Handler(0xb7f6a0, 0xc000078140, 0xc8ea60, 0xc000302150, 0xc00009c6c0, 0x0, 0xc8ea60, 0xc000302150, 0x0, 0x0)
        github.com/hashicorp/[email protected]/tfprotov5/internal/tfplugin5/tfplugin5_grpc.pb.go:434 +0x214
google.golang.org/grpc.(*Server).processUnaryRPC(0xc0000c6380, 0xc95578, 0xc000310d80, 0xc0001a0000, 0xc0001fec90, 0x104f188, 0x0, 0x0, 0x0)
        google.golang.org/[email protected]/server.go:1194 +0x52b
google.golang.org/grpc.(*Server).handleStream(0xc0000c6380, 0xc95578, 0xc000310d80, 0xc0001a0000, 0x0)
        google.golang.org/[email protected]/server.go:1517 +0xd0c
google.golang.org/grpc.(*Server).serveStreams.func1.2(0xc0000223a0, 0xc0000c6380, 0xc95578, 0xc000310d80, 0xc0001a0000)
        google.golang.org/[email protected]/server.go:859 +0xab
created by google.golang.org/grpc.(*Server).serveStreams.func1
        google.golang.org/[email protected]/server.go:857 +0x1fd

Error: The terraform-provider-htpasswd_v0.9.1 plugin crashed!

This is always indicative of a bug within the plugin. It would be immensely
helpful if you could report the crash with the plugin's maintainers so that it
can be fixed. The output above should help diagnose the issue.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant