FIX: Error occurs when you try to deploy CU5 or CU6 for SQL Server 2019 BDC irrespective of the azdata version

Applies to: SQL Server 2019 on Linux

Symptoms


You try to deploy Microsoft SQL Server 2019 Big Data Cluster (BDC) Cumulative Update 5 (CU5) or Cumulative Update 6 (CU6) (regardless of the azdata version) on a Kubernetes cluster that's running on RHEL host OS. In this scenario, you notice that the deployment fails and returns the following error message:

DateTime [LAUNCH] The process"grafana" exists and returns error: The process exited with code '1'and error: exit status 1
DateTime [LAUNCH] Starting to force stopprocess "grafana"
DateTime The process launcher"grafana" exited: Failed to force stop the process"grafana": no such process

Status


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. 

Resolution


This issue is fixed in the following cumulative update for SQL Server:
About cumulative updates for SQL Server:
Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. Check out the latest cumulative updates for SQL Server:

Workaround


To work around this issue, you can add “security”: { “allowRunAsRoot”: true } in the Control.json file to unlock the deployment.

References


Learn about the terminology that Microsoft uses to describe software updates.