You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
╷
│ Error: checking for presence of existing Monitor Diagnostic Setting "worker-diagnostic-logs"for Resource "/subscriptions/5f7f3495-660d-40b7-8bc1-6f36a22c7565/resourceGroups/nucleus-dev-contracts/providers/Microsoft.Web/sites/vs-nucleus-dev-contracts-worker": diagnosticsettings.DiagnosticSettingsClient#Get: Failure responding to request: StatusCode=500 -- Original Error: autorest/azure: Service returned an error. Status=500 Code="Unknown" Message="Unknown service error" Details=[{"code":"InternalServerError","message":""}]
│
│ with module.service.azurerm_monitor_diagnostic_setting.function_diagnostic_log["worker"],
│ on .terraform/modules/service/terraform/modules/services/web_api/function_app.tf line 320, in resource "azurerm_monitor_diagnostic_setting""function_diagnostic_log":
│ 320: resource "azurerm_monitor_diagnostic_setting""function_diagnostic_log" {
│
╵
##[error]Script failed with error: Error: The process '/usr/bin/bash' failed with exit code 1
at ExecState._setResult (/agent/_work/_tasks/AzureCLI_46e4be58-730b-4389-8a2f-ea10b3e5e815/1.238.4/node_modules/azure-pipelines-task-lib/toolrunner.js:1219:25)
at ExecState.CheckComplete (/agent/_work/_tasks/AzureCLI_46e4be58-730b-4389-8a2f-ea10b3e5e815/1.238.4/node_modules/azure-pipelines-task-lib/toolrunner.js:1202:18)
at ChildProcess.<anonymous> (/agent/_work/_tasks/AzureCLI_46e4be58-730b-4389-8a2f-ea10b3e5e815/1.238.4/node_modules/azure-pipelines-task-lib/toolrunner.js:1115:19)
at ChildProcess.emit (node:events:513:28)
at maybeClose (node:internal/child_process:1100:16)
at Process.ChildProcess._handle.onexit (node:internal/child_process:304:5)
Expected Behaviour
Existing Diagnotic settings must be read during plan or new must be created
Actual Behaviour
terraform fails in both step in reading the resource in plan and create in apply step
Steps to Reproduce
Create an azure function and try to enable diagnostic setting on azure function using azurerm_monitor_diagnostic_setting
Important Factoids
No response
References
No response
The text was updated successfully, but these errors were encountered:
Hi @findajay ,
The Status=500 Code="Unknown" Message="Unknown service error" Details=[{"code":"InternalServerError","message":""}] error message should be backend issue which means the API has some error. I am unable to reproduce it with below config. Could you please reproduce it with the latest provider 3.111.0 version and provide the config which can be reproduced? thanks.
Is there an existing issue for this?
Community Note
Terraform Version
1.3.7
AzureRM Provider Version
3.75.0
Affected Resource(s)/Data Source(s)
azurerm_monitor_diagnostic_setting
Terraform Configuration Files
Debug Output/Panic Output
Expected Behaviour
Existing Diagnotic settings must be read during plan or new must be created
Actual Behaviour
terraform fails in both step in reading the resource in plan and create in apply step
Steps to Reproduce
Create an azure function and try to enable diagnostic setting on azure function using azurerm_monitor_diagnostic_setting
Important Factoids
No response
References
No response
The text was updated successfully, but these errors were encountered: