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

Metastore deployment fails with context deadline exceeded #332

Closed
jjgriff93 opened this issue Sep 22, 2023 · 0 comments · Fixed by #333
Closed

Metastore deployment fails with context deadline exceeded #332

jjgriff93 opened this issue Sep 22, 2023 · 0 comments · Fixed by #333
Assignees
Labels
bug Something isn't working needs: triage Item is pending initial response by a maintainer.

Comments

@jjgriff93
Copy link
Member

Describe the bug
Terraform is unable to communicate with the metastore storage account once created:

  │ Error: reading static website for AzureRM Storage Account "stgmricdbksucprod": accounts.Client#GetServiceProperties: Failure sending request: StatusCode=0 -- Original Error: context deadline exceeded
  │ 
  │   with module.unity_catalog_metastore[0].azurerm_storage_account.unity_catalog,
  │   on unity-catalog-metastore/metastore.tf line 41, in resource "azurerm_storage_account" "unity_catalog":
  │   41: resource "azurerm_storage_account" "unity_catalog" {
  │ 

This is because the DNS zone associations in the private link configuration are mismatched:

  for_each = {
    "dfs"  = var.private_dns_zones["blob"].id
    "blob" = var.private_dns_zones["dfs"].id
  }
@jjgriff93 jjgriff93 added the bug Something isn't working label Sep 22, 2023
@jjgriff93 jjgriff93 self-assigned this Sep 22, 2023
@github-actions github-actions bot added the needs: triage Item is pending initial response by a maintainer. label Sep 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working needs: triage Item is pending initial response by a maintainer.
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

1 participant