Getting issues using Sql action while performing deployment on Azure SQL Server using self hosted agent hosted in Azure kubernetes services
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- azure, github-actions, kubernetes, sql
- Domain
- authentication, ci-cd, cloud, databases
Research direction
Start with the workflow step invoking azure/sql-action@v2.3 and the sqlcmd command shown in the report. Compare authentication and environment differences between the GitHub-hosted runner and the self-hosted AKS runner, including the OIDC service principal setup. Done means identifying the missing configuration or permission that causes the token-identified principal login failure.
Written by the indexing model from the issue text.
Description
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
- Dominant language
- TypeScript
- Stars
- 142
- Forks
- 73
- Avg merge
- 9d 18h
- Merged PRs (30d)
- 2
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Azure/sql-action
-
need-to-triage
Difficulty 1/5 Under an hour Newbie friendliness 62/100
Azure/sql-action#247 ·
-
need-to-triage
Difficulty 3/5 1-2 days Newbie friendliness 65/100
Azure/sql-action#282 ·
-
bug
Azure/sql-action#267 · 1 assignee ·
-
need-to-triage
Difficulty 3/5 1-2 days Newbie friendliness 45/100
Azure/sql-action#262 · 1 comment ·
-
need-to-triage
Difficulty 3/5 1-2 days Newbie friendliness 35/100
Azure/sql-action#261 ·
All issues in Azure/sql-action
Similar issues
-
blocklist removal
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
MetaMask/eth-phishing-detect#296544 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
pastelsky/bundlephobia#1122 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
category/development priority/P2 scope/file-operations scope/testing type/enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Enatega Customer and Rider app: Add-ons price is not visible to customer after order is placed. Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100