Skip to content

Instantly share code, notes, and snippets.

@JensvandeWiel
Last active January 25, 2026 12:38
Show Gist options
  • Select an option

  • Save JensvandeWiel/66841718f25694ee54b05bbfc7fc5bcb to your computer and use it in GitHub Desktop.

Select an option

Save JensvandeWiel/66841718f25694ee54b05bbfc7fc5bcb to your computer and use it in GitHub Desktop.

Error itself

╷
│ Error: Provider produced inconsistent final plan
│ 
│ When expanding the plan for kubernetes_namespace_v1.argocd to include new values learned so far during apply, provider "registry.opentofu.org/hashicorp/kubernetes" produced an invalid new value for
│ .id: was null, but now cty.UnknownVal(cty.String).
│ 
│ This is a bug in the provider, which should be reported in the provider's own issue tracker.
╵
╷
│ Error: Provider produced inconsistent final plan
│ 
│ When expanding the plan for kubernetes_namespace_v1.argocd to include new values learned so far during apply, provider "registry.opentofu.org/hashicorp/kubernetes" produced an invalid new value for
│ .wait_for_default_service_account: was null, but now cty.False.
│ 
│ This is a bug in the provider, which should be reported in the provider's own issue tracker.
╵
╷
│ Error: Provider produced inconsistent final plan
│ 
│ When expanding the plan for kubernetes_namespace_v1.argocd to include new values learned so far during apply, provider "registry.opentofu.org/hashicorp/kubernetes" produced an invalid new value for
│ .metadata[0].resource_version: was null, but now cty.UnknownVal(cty.String).
│ 
│ This is a bug in the provider, which should be reported in the provider's own issue tracker.
╵
╷
│ Error: Provider produced inconsistent final plan
│ 
│ When expanding the plan for kubernetes_namespace_v1.argocd to include new values learned so far during apply, provider "registry.opentofu.org/hashicorp/kubernetes" produced an invalid new value for
│ .metadata[0].uid: was null, but now cty.UnknownVal(cty.String).
│ 
│ This is a bug in the provider, which should be reported in the provider's own issue tracker.
╵
╷
│ Error: Provider produced inconsistent final plan
│ 
│ When expanding the plan for kubernetes_namespace_v1.argocd to include new values learned so far during apply, provider "registry.opentofu.org/hashicorp/kubernetes" produced an invalid new value for
│ .metadata[0].generation: was null, but now cty.UnknownVal(cty.Number).
│ 
│ This is a bug in the provider, which should be reported in the provider's own issue tracker.
╵

Part of debug trace

2026-01-25T13:22:16.843+0100 [DEBUG] State storage *statemgr.Filesystem declined to persist a state snapshot
2026-01-25T13:22:16.844+0100 [DEBUG] provider.stdio: received EOF, stopping recv loop: err="rpc error: code = Unavailable desc = error reading from server: EOF"
2026-01-25T13:22:16.845+0100 [INFO]  provider: plugin process exited: plugin=.terraform/providers/registry.opentofu.org/hashicorp/http/3.5.0/linux_amd64/terraform-provider-http id=53512
2026-01-25T13:22:16.845+0100 [DEBUG] provider: plugin exited
2026-01-25T13:22:16.848+0100 [WARN]  Provider "provider[\"registry.opentofu.org/hashicorp/kubernetes\"]" produced an invalid plan for kubernetes_namespace_v1.argocd, 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:
      - .wait_for_default_service_account: planned value cty.False for a non-computed attribute
2026-01-25T13:22:16.848+0100 [ERROR] vertex "kubernetes_namespace_v1.argocd" error: Provider produced inconsistent final plan
2026-01-25T13:22:16.848+0100 [ERROR] vertex "kubernetes_namespace_v1.argocd" error: Provider produced inconsistent final plan
2026-01-25T13:22:16.848+0100 [ERROR] vertex "kubernetes_namespace_v1.argocd" error: Provider produced inconsistent final plan
2026-01-25T13:22:16.848+0100 [ERROR] vertex "kubernetes_namespace_v1.argocd" error: Provider produced inconsistent final plan
2026-01-25T13:22:16.848+0100 [ERROR] vertex "kubernetes_namespace_v1.argocd" error: Provider produced inconsistent final plan
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment