Running 2017-latest on AKS cluster

[HippyRock]

Hi, I'm trying to run sql server on AKS cluster (v1.14) on Linux node.
I'm able successfully run server:2017-latest or server:2017-latest-ubuntu on my development machine on latest docker ce. As well as directly on cluster node by using:

sudo docker run -e 'ACCEPT_EULA=Y' -e 'SA_PASSWORD=<YourStrong!Passw0rd>' \
   -p 1433:1433 --name sql1 \
   -d mcr.microsoft.com/mssql/server:2017-latest

But when I try to deploy it on cluster it fails with various errors, for example:

2019-06-06 17:52:14.61 spid6s      Error: 17120, Severity: 16, State: 0.
2019-06-06 17:52:14.61 spid6s      SQL Server could not spawn HADRON Manager thread. Check the SQL Server error log and the operating system error log for information about possible related problems.
2019-06-06 17:52:14.62 spid6s      Startup of Always On Availability Groups replica manager failed due to SQL Server error 17120.  To determine the cause of this error, check the SQL Server error log for the preceding error.
2019-06-06 17:52:14.62 spid9s      Starting up database 'mssqlsystemresource'.
2019-06-06 17:52:14.62 spid6s      Starting up database 'msdb'.
2019-06-06 17:52:14.63 spid9s      The resource database build version is 14.00.3162. This is an informational message only. No user action is required.
2019-06-06 17:52:14.66 spid9s      Starting up database 'model'.
2019-06-06 17:52:14.73 spid10s     A self-generated certificate was successfully loaded for encryption.
2019-06-06 17:52:14.75 spid10s     Server is listening on [ 'any' <ipv6> 1433].
2019-06-06 17:52:14.75 spid10s     Server is listening on [ 'any' <ipv4> 1433].
2019-06-06 17:52:14.98 spid9s      Polybase feature disabled.
2019-06-06 17:52:14.98 spid9s      Clearing tempdb database.
2019-06-06 17:52:15.82 spid9s      Starting up database 'tempdb'.
2019-06-06 17:52:16.16 spid9s      The tempdb database has 1 data file(s).
2019-06-06 17:52:33.24 Server      Software Usage Metrics is disabled.
2019-06-06 17:52:34.04 Server      Failed to verify the Authenticode signature of 'C:\binn\secforwarder.dll'. Signature verification of SQL Server DLLs will be skipped. Genuine copies of SQL Server are signed. Failure to verify the Authenticode signature might indicate that this is not an authentic release of SQL Server. Install a genuine copy of SQL Server or contact customer support.
2019-06-06 17:53:53.28 Server      Server is listening on [ ::1 <ipv6> 1434].
2019-06-06 17:53:53.28 Server      Server is listening on [ 127.0.0.1 <ipv4> 1434].
2019-06-06 17:53:53.28 Server      Dedicated admin connection support was established for listening locally on port 1434.
2019-06-06 17:53:53.28 spid10s     Recovery is complete. This is an informational message only. No user action is required.
2019-06-06 17:53:53.28 spid10s     SQL Server is now ready for client connections. This is an informational message; no user action is required.
2019-06-06 17:53:53.31 spid34s     The Service Broker endpoint is in disabled or stopped state.
2019-06-06 17:53:53.34 spid34s     The Database Mirroring endpoint is in disabled or stopped state.
2019-06-06 17:53:53.36 spid34s     Service Broker manager has started.
This program has encountered a fatal error and cannot continue running at Thu Jun  6 17:57:17 2019
The following diagnostic information is available:

       Reason: 0x00000006
      Message: Last Chance
      Address: 0x14c7437d1
   Parameters: 0x51eb0b9b0
   Stack Trace:
               000000006b732f12

I'm using this yaml:

apiVersion: extensions/v1beta1
kind: Deployment
metadata:
  name: sqlblank
  labels:
    app: sqlblank
spec:
  replicas: 1
  template:
    metadata:
      name: sqlblank
      labels:
        app: sqlblank
    spec:
      terminationGracePeriodSeconds: 10
      containers:
      - image: mcr.microsoft.com/mssql/server:2017-latest-ubuntu
        name: sqlblank
        ports:
        - containerPort: 1433
        env:
        - name: MSSQL_PID
          value: "Developer"
        - name: ACCEPT_EULA
          value: "Y"
        - name: MSSQL_SA_PASSWORD
          value: "<Password>"
        resources: {}
      restartPolicy: Always
      imagePullSecrets:
        - name: vberegistrysecret
      nodeSelector:
        name: linux1
  selector:
    matchLabels:
      app: sqlblank

I tried different images such as microsoft/mssql-server-linux, server:2019-CTP3.0-ubuntu with the same results. Any ideas what is wrong?

[minican]

Hi
You could try to check the following cu article
https://support.microsoft.com/en-my/help/4484710/cumulative-update-14-for-sql-server-2017

[HippyRock]

Hi! I'm running mcr.microsoft.com/mssql/server:2017-latest-ubuntu
which already includes CU15:

> kubectl logs sqlblank-5d5cc56c4-lmrch
2019-06-06 17:52:13.13 Server      Microsoft SQL Server 2017 (RTM-CU15) (KB4498951) - 14.0.3162.1 (X64)
        May 15 2019 19:14:30
        Copyright (C) 2017 Microsoft Corporation
        Developer Edition (64-bit) on Linux (Ubuntu 16.04.6 LTS)

[Zetanova]

looks the same as #441

What Storage was used?