Closed satishraj777 closed 10 months ago
Thanks for reporting! @lijinpei2008 please look into this issue and let's discuss this week.
Hello @isra-fel and @lijinpei2008 Any update on this ticket? Our customer is expecting a fix on this and is not willing to close the ticket at our end. Please prioritize this and help us with any update.
The fix was merged and will be available in the next release on Nov. 15th.
Closing as fixed.
Description
Steps to reproduce
1) Create a premium workspace with prepare encryption false.
2) Update workspace with CMK on Managed Services by running the below command
**Update-AzDatabricksWorkspace -SubscriptionId <subid> -ResourceGroupName <resourceGroup> -Name <nameofWorkspace> -ManagedServicesKeyVaultPropertiesKeyName '<keyname>' -ManagedServicesKeyVaultPropertiesKeyVaultUri '<keyvaultURI>' -ManagedServicesKeyVaultPropertiesKeyVersion '<keyversion>'**
Result: CMK on managed services should be configured successfully
3) Now, update workspace with CMK on DBFS or try to update CMK with prepareEncryption == true using below commands
Update-AzDatabricksWorkspace -ResourceGroupName <resourceGroup> -Name <nameofWorkspace> -EncryptionKeySource Microsoft.Keyvault -EncryptionKeyName <keyname> -EncryptionKeyVersion <keyversion>-EncryptionKeyVaultUri <keyvaultURI>
Update-AzDatabricksWorkspace -SubscriptionId <subid> -ResourceGroupName <resourceGroup> -Name <nameofWorkspace> -PrepareEncryption
Expected Result:
1) Workspace should be updated with prepareEncryption true
2) DBFS encryption should fail with either two validations:
account
According to the traces trim correlation result, from the request payload we see that managedDisk is being called while we are only trying to update prepareEncryption or DBFS encryption.
Issue script & Debug output
Environment data
Module versions
Error output