Skip to content

SKE: inconsistent result after apply #1150

@HartmannVolker

Description

@HartmannVolker

Description

After changing my node_pool configuration I saw this error in the terraform output:

│ Error: Provider produced inconsistent result after apply
│ 
│ When applying changes to module.prod_cluster.stackit_ske_cluster.this,
│ provider "provider[\"registry.terraform.io/stackitcloud/stackit\"]"
│ produced an unexpected new value: .node_pools[1].max_unavailable: was null,
│ but now cty.NumberIntVal(0).
│ 
│ This is a bug in the provider, which should be reported in the provider's
│ own issue tracker.
╵
╷
│ Error: Provider produced inconsistent result after apply
│ 
│ When applying changes to module.prod_cluster.stackit_ske_cluster.this,
│ provider "provider[\"registry.terraform.io/stackitcloud/stackit\"]"
│ produced an unexpected new value: .node_pools[1].labels: was null, but now
│ cty.MapValEmpty(cty.String).
│ 
│ This is a bug in the provider, which should be reported in the provider's
│ own issue tracker.
╵

I created a node pool with maximum = "1" & max_surge = "1". max_unavailable & labels are both unset in my terraform config.

The error has resolved after a second apply.

Actual behavior

Errors are shown after apply.

Expected behavior

No Errors are shown after apply.

Environment

  • OS: MacOS 26.2
  • Terraform version (see terraform --version): v1.13.5
  • Version of the STACKIT Terraform provider: 0.76.0

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions