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

terraform apply freezing #4

Open
finnless opened this issue Sep 18, 2023 · 0 comments
Open

terraform apply freezing #4

finnless opened this issue Sep 18, 2023 · 0 comments

Comments

@finnless
Copy link

I'm following the instructions in the readme, but am running into issues when running terraform apply.
I'm interrupting after a few minutes of nothing.
Here is a log dump with TF_LOG=INFO. Let me know if there is any other info I can provide. @thunderbug1

vscode ➜ /workspaces/LibreChatAzureDeployment (main) $ terraform apply
2023-09-18T04:04:18.248Z [INFO]  Terraform version: 1.5.7
2023-09-18T04:04:18.248Z [INFO]  Go runtime version: go1.20.7
2023-09-18T04:04:18.248Z [INFO]  CLI args: []string{"terraform", "apply"}
2023-09-18T04:04:18.249Z [INFO]  CLI command args: []string{"apply"}
2023-09-18T04:04:18.434Z [INFO]  backend/local: starting Apply operation
2023-09-18T04:04:18.437Z [INFO]  provider: configuring client automatic mTLS
2023-09-18T04:04:18.515Z [INFO]  provider.terraform-provider-azurerm_v3.73.0_x5: configuring server automatic mTLS: timestamp=2023-09-18T04:04:18.515Z
2023-09-18T04:04:18.681Z [INFO]  provider: configuring client automatic mTLS
2023-09-18T04:04:18.704Z [INFO]  provider.terraform-provider-random_v3.3.2_x5: configuring server automatic mTLS: timestamp=2023-09-18T04:04:18.704Z
2023-09-18T04:04:18.726Z [INFO]  provider: configuring client automatic mTLS
2023-09-18T04:04:18.751Z [INFO]  provider.terraform-provider-random_v3.3.2_x5: configuring server automatic mTLS: timestamp=2023-09-18T04:04:18.751Z
2023-09-18T04:04:18.767Z [INFO]  provider: configuring client automatic mTLS
2023-09-18T04:04:18.826Z [INFO]  provider.terraform-provider-azurerm_v3.73.0_x5: configuring server automatic mTLS: timestamp=2023-09-18T04:04:18.826Z
2023-09-18T04:04:19.011Z [INFO]  backend/local: apply calling Plan
2023-09-18T04:04:19.013Z [INFO]  provider: configuring client automatic mTLS
2023-09-18T04:04:19.074Z [INFO]  provider.terraform-provider-azurerm_v3.73.0_x5: configuring server automatic mTLS: timestamp=2023-09-18T04:04:19.074Z
2023-09-18T04:04:19.148Z [INFO]  provider: configuring client automatic mTLS
2023-09-18T04:04:19.177Z [INFO]  provider.terraform-provider-random_v3.3.2_x5: configuring server automatic mTLS: timestamp=2023-09-18T04:04:19.177Z
2023-09-18T04:04:19.202Z [WARN]  Provider "registry.terraform.io/hashicorp/random" produced an invalid plan for random_string.mongo_root_password, but we are tolerating it because it is using the legacy plugin SDK.
    The following problems may be the cause of any confusing errors from downstream operations:
      - .min_lower: planned value cty.NumberIntVal(0) for a non-computed attribute
      - .min_numeric: planned value cty.NumberIntVal(0) for a non-computed attribute
      - .min_upper: planned value cty.NumberIntVal(0) for a non-computed attribute
      - .min_special: planned value cty.NumberIntVal(0) for a non-computed attribute
2023-09-18T04:04:19.203Z [WARN]  Provider "registry.terraform.io/hashicorp/random" produced an invalid plan for random_string.creds_key, but we are tolerating it because it is using the legacy plugin SDK.
    The following problems may be the cause of any confusing errors from downstream operations:
      - .min_lower: planned value cty.NumberIntVal(0) for a non-computed attribute
      - .min_numeric: planned value cty.NumberIntVal(0) for a non-computed attribute
      - .min_upper: planned value cty.NumberIntVal(0) for a non-computed attribute
      - .min_special: planned value cty.NumberIntVal(0) for a non-computed attribute
2023-09-18T04:04:19.203Z [WARN]  Provider "registry.terraform.io/hashicorp/random" produced an invalid plan for random_string.random_postfix, but we are tolerating it because it is using the legacy plugin SDK.
    The following problems may be the cause of any confusing errors from downstream operations:
      - .min_upper: planned value cty.NumberIntVal(0) for a non-computed attribute
      - .min_special: planned value cty.NumberIntVal(0) for a non-computed attribute
      - .min_lower: planned value cty.NumberIntVal(0) for a non-computed attribute
      - .min_numeric: planned value cty.NumberIntVal(0) for a non-computed attribute
2023-09-18T04:04:19.203Z [WARN]  Provider "registry.terraform.io/hashicorp/random" produced an invalid plan for random_string.creds_iv, but we are tolerating it because it is using the legacy plugin SDK.
    The following problems may be the cause of any confusing errors from downstream operations:
      - .min_special: planned value cty.NumberIntVal(0) for a non-computed attribute
      - .min_lower: planned value cty.NumberIntVal(0) for a non-computed attribute
      - .min_numeric: planned value cty.NumberIntVal(0) for a non-computed attribute
      - .min_upper: planned value cty.NumberIntVal(0) for a non-computed attribute
2023-09-18T04:04:19.203Z [WARN]  Provider "registry.terraform.io/hashicorp/random" produced an invalid plan for random_string.meilisearch_master_key, but we are tolerating it because it is using the legacy plugin SDK.
    The following problems may be the cause of any confusing errors from downstream operations:
      - .min_special: planned value cty.NumberIntVal(0) for a non-computed attribute
      - .upper: planned value cty.True for a non-computed attribute
      - .min_lower: planned value cty.NumberIntVal(0) for a non-computed attribute
      - .min_numeric: planned value cty.NumberIntVal(0) for a non-computed attribute
      - .min_upper: planned value cty.NumberIntVal(0) for a non-computed attribute
      - .lower: planned value cty.True for a non-computed attribute
2023-09-18T04:04:19.204Z [WARN]  Provider "registry.terraform.io/hashicorp/random" produced an invalid plan for random_string.jwt_secret, but we are tolerating it because it is using the legacy plugin SDK.
    The following problems may be the cause of any confusing errors from downstream operations:
      - .min_special: planned value cty.NumberIntVal(0) for a non-computed attribute
      - .min_numeric: planned value cty.NumberIntVal(0) for a non-computed attribute
      - .min_lower: planned value cty.NumberIntVal(0) for a non-computed attribute
      - .min_upper: planned value cty.NumberIntVal(0) for a non-computed attribute
2023-09-18T04:04:19.256Z [WARN]  ValidateProviderConfig from "provider[\"registry.terraform.io/hashicorp/azurerm\"]" changed the config value, but that value is unused
^C
Interrupt received.
Please wait for Terraform to exit or data loss may occur.
Gracefully shutting down...

^C
Two interrupts received. Exiting immediately. Note that data loss may have occurred.

╷
│ Error: operation canceled
│ 
│ 
╵
2023-09-18T04:06:30.157Z [ERROR] plugin.(*GRPCProvider).ConfigureProvider: error="rpc error: code = Unavailable desc = error reading from server: EOF"
2023-09-18T04:06:30.157Z [ERROR] vertex "provider[\"registry.terraform.io/hashicorp/azurerm\"]" error: Plugin did not respond

Terraform used the selected providers to generate the following execution plan. Resource actions are indicated with
the following symbols:
  + create

Terraform planned the following actions, but then encountered a problem:

  # random_string.creds_iv will be created
  + resource "random_string" "creds_iv" {
      + id          = (known after apply)
      + length      = 32
      + lower       = true
      + min_lower   = 0
      + min_numeric = 0
      + min_special = 0
      + min_upper   = 0
      + number      = true
      + numeric     = true
      + result      = (known after apply)
      + special     = false
      + upper       = false
    }

  # random_string.creds_key will be created
  + resource "random_string" "creds_key" {
      + id          = (known after apply)
      + length      = 64
      + lower       = true
      + min_lower   = 0
      + min_numeric = 0
      + min_special = 0
      + min_upper   = 0
      + number      = true
      + numeric     = true
      + result      = (known after apply)
      + special     = false
      + upper       = false
    }

  # random_string.jwt_secret will be created
  + resource "random_string" "jwt_secret" {
      + id          = (known after apply)
      + length      = 64
      + lower       = true
      + min_lower   = 0
      + min_numeric = 0
      + min_special = 0
      + min_upper   = 0
      + number      = true
      + numeric     = true
      + result      = (known after apply)
      + special     = false
      + upper       = false
    }

  # random_string.meilisearch_master_key will be created
  + resource "random_string" "meilisearch_master_key" {
      + id          = (known after apply)
      + length      = 20
      + lower       = true
      + min_lower   = 0
      + min_numeric = 0
      + min_special = 0
      + min_upper   = 0
      + number      = true
      + numeric     = true
      + result      = (known after apply)
      + special     = false
      + upper       = true
    }

  # random_string.mongo_root_password will be created
  + resource "random_string" "mongo_root_password" {
      + id          = (known after apply)
      + length      = 32
      + lower       = true
      + min_lower   = 0
      + min_numeric = 0
      + min_special = 0
      + min_upper   = 0
      + number      = true
      + numeric     = true
      + result      = (known after apply)
      + special     = false
      + upper       = false
    }

  # random_string.random_postfix will be created
  + resource "random_string" "random_postfix" {
      + id          = (known after apply)
      + length      = 8
      + lower       = true
      + min_lower   = 0
      + min_numeric = 0
      + min_special = 0
      + min_upper   = 0
      + number      = true
      + numeric     = true
      + result      = (known after apply)
      + special     = false
      + upper       = false
    }

Plan: 6 to add, 0 to change, 0 to destroy.
╷
│ Error: Plugin did not respond
│ 
│   with provider["registry.terraform.io/hashicorp/azurerm"],
│   on providers.tf line 17, in provider "azurerm":
│   17: provider "azurerm" {
│ 
│ The plugin encountered an error, and failed to respond to the plugin.(*GRPCProvider).ConfigureProvider call. The
│ plugin logs may contain more details
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