search

Azure / Test-Drive-Azure-Synapse-with-a-1-click-POC

MIT License
61 stars 459 forks source link

Deployment failure #4

Closed ralphke closed 3 years ago

ralphke commented 3 years ago

When deploying this resources to Azure, I get this error:

{ "status": "Failed", "error": { "code": "BadRequest", "message": "Content-Type header value missing.", "details": [] } } Type: Microsoft.Synapse/workspaces/sqlPools/transparentDataEncryption Ressource ID /subscriptions/1f66d329-d23b-4303-acbd-cc4b98f9456e/resourceGroups/1-Click-POC/providers/Microsoft.Synapse/workspaces/conesxkzpg6mdfo2pocws1/sqlPools/conesxkzpg6mdfo2pocws1p1/transparentDataEncryption/current Deployment Correlation ID f81c36f2-f701-4205-b4ed-f71f36fcaaba Timestamp: 12.8.2021, 12:41:02

How to fix this repro to make it work? Wouldn't it be much easier to provide a pre-provisioned service for registered users with a given ACR budget?

alpinedelight commented 3 years ago

Same here - however, it does seem to have enabled it when inspecting the dedicated warehouse. image

ralphke commented 3 years ago

To me it looks like the transparentEncyption option gets a wrong parameter set.

roberts-andy commented 3 years ago

i get the same error when i just tried to deploy. It looks like it might be the API Version? In the quickstart at: https://docs.microsoft.com/en-us/azure/synapse-analytics/sql-data-warehouse/quickstart-arm-template?tabs=CLI I see the following api version for transparent data encryption "apiVersion": "2017-03-01-preview", and the template in this repo i see "apiVersion": "2021-03-01",

it could also be that the comment is not added to the TDE resource. i thought i was testing these changes just now but realized i was still using the published template and not the one in my forked repo.

I guess the two larger questions that i have are: 1) Is this something that we want customers to set when deploying? Or should we just leave it at the default enabled. 2) after this failure, is everything else deployed successfully? I havent had a chance to look yet

patsql commented 3 years ago

Same Error here. Please don't give this to customers at this point in time.

atrahul commented 3 years ago

Thank you for the feedback. Bad request was caused due to TDE configuration. This is resolved and it works fine now.