Azure-rest-api-specs: Unalbe to set Storage_URI to null once enabled on boot_diagnostics on VM

[VaijanathB]

Here is the scenario,
1.User creates a VM with boot_diagnostics enabled
2.User disables boot_diagnostics and deletes the Storage Account.
3.When we send the following json blob in the VM payload we expect the server to update the Storage_URI to null.
"diagnosticsProfile": {
"bootDiagnostics": {
"enabled": false,
"storageUri": ""
}
},
4.Even though the boot_diagnostics is disabled, the storage_uri variable still has the old value which is returned to the user in the GET api. This is an issue and needs to be fixed.

[marstr]

Triaged, removing my assignment.

[rohrerb]

@marstr - Could i get a update on this?

[salameer]

@hyonholee would you happen to have an contact to look into this issue?

[rem-aj]

Guys I have a temporary workaround for this so it does not always show up as a change in your "create_plan" until the fix is out. Use the ignore parameter in your vm create resource on those boot diagnostics properties.

[rem-aj]

Hi @bsiegel what does the status "Service Attention" mean and is it possible for us to get an ETA on when this issue will be resolved.
Thanks!

[bsiegel]

Hi @bostonmoto - Service Attention means that ownership of this issue has been handed off to the Azure Compute team to solve, as it relates to the service itself rather than an issue with the API specifications themselves.

@salameer can you help track down what the status of this issue is with the service team? Thanks!

For what it's worth, I apologize for the radio silence on your issue. We've been working to put in place a much smoother pipeline for triaging such issues and making sure that the service teams follow up with our customers in a timely manner, but we're not quite at the point yet where we're seeing the results of those efforts.

[rem-aj]

Thanks for the update @bsiegel. We look forward to hearing from @salameer.

[kenorb]

Still the issue with Terraform v0.11.14.

  ~ module.foobar.azurerm_virtual_machine.notary
      boot_diagnostics.#:             "1" => "0"
      boot_diagnostics.0.storage_uri: "https://tempfoobar.blob.core.windows.net" => ""

Despite _Boot diagnostics are not configured for this virtual machine._.

[MacFlurry]

got same thing.

[ben5556]

Still the issue with Terraform v0.11.14.

  ~ module.foobar.azurerm_virtual_machine.notary
      boot_diagnostics.#:             "1" => "0"
      boot_diagnostics.0.storage_uri: "https://tempfoobar.blob.core.windows.net" => ""

Despite _Boot diagnostics are not configured for this virtual machine._.

Running into this issue as well. We are creating a VM with boot diagnostics enabled set to false but it appears storage_uri is a required parameter even when we set diagnostics to disabled... :-(