azure next-gen databricks disconnected causes updateRawBody: failed to unmarshal response body

[tusharshahrs]

Working on azurenext-gen databricks:

We are able to get the databricks peering with another virtual network in the same region and same subscription.

I shutdown the peering via pulumi and then saw that the databricks vnet peering was in disconnected state According to ms a disconnected peering states to delete the peer from both networks and re-create the peering.

When I reinitialize the peering via pulumi up I get the following error:
error: pollingTrackerBase#updateRawBody: failed to unmarshal response body: StatusCode=0 -- Original Error: json: cannot unmarshal string into Go value of type map[string]interface {}

Why would it occur. I can tear down databricks and restart it from scratch. But if I was a customer, and couldn’t tear down the databricks, how would I get past this issue?

Steps to reproduce: Everything is in azure nextgen and in python

1. Set up azure next gen virtual network with 2 subnets. mkdir azure-nextgen-virtualnetwork-py cd azure-nextgen-virtualnetwork-py git clone: https://github.com/tusharshahrs/pulumi-homelab/tree/aws_eks/azure-nextgen-virtualnetwork-py pulumi stack init dev pulumi up -y

2. Launch databricks mkdir azure-nextgen-databricks cd azure-nextgen-databricks git clone: https://github.com/tusharshahrs/pulumi-homelab/tree/aws_eks/azure-nextgen-databricks pulumi stack init dev pulumi config set mysubid REPLACE_THIS_WITH_WHATEVER_YOUR_AZURE_SUBSCRIPTION_IS pulumi up -y

3. Launch vnetpeering mkdir azure-nextgen-vnetpeering-py cd azure-nextgen-vnetpeering-py git clone: https://github.com/tusharshahrs/pulumi-homelab/tree/aws_eks/azure-nextgen-vnetpeering-py pulumi stack init dev pulumi config set mysubid REPLACE_THIS_WITH_WHATEVER_YOUR_AZURE_SUBSCRIPTION_IS pulumi up -y

4. Check out the virtual network and peering status showed show: CONNECTED

5. Tear down the peering connection. cd azure-nextgen-vnetpeering-py pulumi destroy -y

6. Validate that the virtual network connection in DATABRICKS shows: DISCONNECTED https://share.getcloudapp.com/Wnur9vNp

7. As per ms, we need to recreate the peering connection. The peering connection is gone from the virtual network1. We need to tear it down from databricks. comment out the following vnet peering code in the databricks: https://github.com/tusharshahrs/pulumi-homelab/blob/aws_eks/azure-nextgen-databricks/__main__.py#L66-L77 cd azure-nextgen-databricks pulumi up -y uncomment out the following vnet peering code in the databricks: https://github.com/tusharshahrs/pulumi-homelab/blob/aws_eks/azure-nextgen-databricks/__main__.py#L66-L77

cd azure-nextgen-databricks pulumi refresh pulumi up -y

[mikhailshilkov]

git clone

was there a link here?

[tusharshahrs]

Logs from pulumi up -y logtostderr -v9 --debug mylogs.txt

[tusharshahrs]

@mikhailshilkov yes, updated with all the links