microsoft / microsoft/sql-server-samples
Azure AKS Services build for SQL 2019 Always-on AG
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 11.2k
- Forks
- 9.1k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 14
Description
I am trying to build AG on Azure AKS using the following 3 yaml .
operator.yaml
sqlserver.yaml
there is problem when starting up the pod/containers for the 3 pod mssql1-0 , mssql2-0 and mssql3-0 . It keep saying
State: Waiting
Reason: CrashLoopBackOff
Last State: Terminated
Reason: Error
Exit Code: 139
Started: Wed, 03 Jun 2020 14:22:34 +0800
Finished: Wed, 03 Jun 2020 14:22:34 +0800
Any idea for this ?
describe_pod.log
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start by reviewing operator.yaml, sqlserver.yaml, and the attached describe_pod.log for mssql1-0, mssql2-0, and mssql3-0. Investigate the CrashLoopBackOff and exit code 139, then verify that all three pods start successfully without recurring container failures.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, kubernetes, sql
- Domain
- cloud, databases, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100