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_storage_sync_server_endpoint - Provider produced inconsistent result after apply #26014

Closed
1 task done
brentisaacs opened this issue May 17, 2024 · 2 comments
Closed
1 task done

Comments

@brentisaacs
Copy link

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 "+1" or "me too" comments, 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.

Terraform Version

1.8.3

AzureRM Provider Version

3.104.0

Affected Resource(s)/Data Source(s)

azurerm_storage_sync_server_endpoint

Terraform Configuration Files

resource "azurerm_storage_sync_server_endpoint" "sync-server-endpoint" {
  count                      = 1
  name                       = "my-ssse"
  storage_sync_group_id      = "/subscriptions/.../resourceGroups/my-main-rg/providers/microsoft.storagesync/storageSyncServices/my-storagesync-svc/syncGroups/my-ssg"
  registered_server_id       = "/subscriptions/.../resourceGroups/my-main-rg/providers/Microsoft.StorageSync/storageSyncServices/my-storagesync-svc/registeredServers/..."
  server_local_path          = "D:\mypath"
  cloud_tiering_enabled      = true
}

Debug Output/Panic Output

Error: Provider produced inconsistent result after apply
│ 
│ When applying changes to
│ module.my_az_filesync["myfileshare"].azurerm_storage_sync_server_endpoint.sync-server-endpoint[0],
│ provider "provider[\"registry.terraform.io/hashicorp/azurerm\"]" produced
│ an unexpected new value: Root object was present, but now absent.
│ 
│ This is a bug in the provider, which should be reported in the provider's
│ own issue tracker.

##[error]Terraform command 'apply' failed with exit code '1'.

Expected Behaviour

Successful terraform provisioning and state file update

Actual Behaviour

Terraform applied the changes, but showed as a failure and did not update the state file

Steps to Reproduce

  1. terraform apply

Important Factoids

No response

References

No response

@bruceharrison1984
Copy link
Contributor

I believe this was fixed by this PR:
#26204

It should be available in the next release.

@rcskosir
Copy link
Contributor

Thanks for taking the time to submit this issue. It looks like this has been resolved as of #26204. As such, I am going to mark this issue as closed. If that is not the case, please provide additional information including the version in which you are still experiencing this issue, thanks!

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

3 participants