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

azurerm_service_fabric_cluster apply terminates when updating resource configuration that contains a stateless node type #28923

Open
1 task done
williamoconnorme opened this issue Mar 2, 2025 · 0 comments

Comments

@williamoconnorme
Copy link
Contributor

Is there an existing issue for this?

  • I have searched the existing issues

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave comments along the lines of "+1", "me too" or "any updates", they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment and review the contribution guide to help.

I've recently introduced a node type with the configuration is_stateless = true to my azurerm_service_fabric_cluster resource. Since then, resource update operations throw an error while applying the change. The operations in azure do succeed, but the provider appears to not be handling the resource state change while the operation is in progress

... 
CreateOrUpdate: `result.Status` was nil/empty - `op.Status` was "InProgress:{ ...
...

Terraform Version

1.7.5

AzureRM Provider Version

3.117.0

Affected Resource(s)/Data Source(s)

azurerm_service_fabric_cluster

Terraform Configuration Files

resource "azurerm_service_fabric_cluster" "example" {
  name                 = "example-servicefabric"
  resource_group_name  = azurerm_resource_group.example.name
  location             = azurerm_resource_group.example.location
  reliability_level    = "Bronze"
  upgrade_mode         = "Manual"
  cluster_code_version = "7.1.456.959"
  vm_image             = "Windows"
  management_endpoint  = "https://example:80"

  node_type {
    name                 = "first"
    instance_count       = 3
    is_primary           = true
    client_endpoint_port = 2020
    http_endpoint_port   = 80
  }
  node_type {
    name                 = "second"
    instance_count       = 2
    is_stateless         = true
    client_endpoint_port = 2020
    http_endpoint_port   = 80
  }
}

Debug Output/Panic Output

https://gist.github.com/williamoconnorme/f8abc275203509dd6d06a2cb2f11bc52

Expected Behaviour

The provider should continue to poll the resource until the operation status changed to complete, rather than prematurely throwing an error while its still in progress

Actual Behaviour

The apply operation returns an error, however the service fabric cluster changes are still being applied within azure and they apply successfully. However a subsequent terraform plan can only be created after the cluster configuration updates finishes deploying

Steps to Reproduce

Deploy a service fabric cluster with at least 1 node_type that has is_stateless set to true

Important Factoids

No response

References

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant