Getting issues using Sql action while performing deployment on Azure SQL Server using self hosted agent hosted in Azure kubernetes services

Finding issues using Sql action while performing deployment on Azure SQL Server using self hosted agent hosted in Azure kubernetes services.

We have noticed that the issue is not facing on Github hosted Runners.

Its on the self hosted runner which we are using on AKS cluster we are using latest version of sql action which is 2.3

Can you guys help us on to differentiate why this is working on github hosted runners and not on self hosted runners hosted by us. Is there any step that needs to be included in the pipeline.

We are using service principal and using OIDC functionality in it we have provided all the required permission to the user on db and have tried all the troubleshooting steps from our end and we are landing on below error.

Run azure/sql-action@v2.3
tar xj --warning=no-unknown-keyword --overwrite -C /runner/_work/_temp/d57370aa-fcb7-4e8c-b169-28598f2b44cb -f /runner/_work/_temp/193f374a-cee2-4b80-a52d-f969488f4c3c
sqlcmd -S xxx.database.windows.net,1433 -d xxx --authentication-method=ActiveDirectoryDefault -i .SQLDB/migration.sql
mssql: login error: Login failed for user ''.
mssql: login error: Login failed for user ''.
Error: The process 'sqlcmd' failed with exit code 1

===

We reached out to github support but as sql action is managed by third party hence they have redirected us to your team.

We can setup a call discuss further on this.

Regards,
Anil Nair

Inizia dal passaggio del workflow che invoca azure/sql-action@v2.3 e il comando sqlcmd mostrato nel report. Confronta le differenze di autenticazione e ambiente tra il runner GitHub-hosted e il runner self-hosted AKS, inclusa la configurazione dell’OIDC service principal. Il lavoro è completato quando viene identificata la configurazione o l’autorizzazione mancante che causa l’errore di accesso del principal identificato dal token.

Scritto dal modello di indicizzazione a partire dal testo della issue.