azure kubernetes version 1.36.2 and sysbox nodepool version is 1.33.13 getting error sysbox failed state
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 3.9k
- Forks
- 230
- Avg merge
- 7h 48m
- Merged PRs (30d)
- 3
Description
azure kubernetes version 1.36.2 and sysbox nodepool version is 1.33.13 getting error
FailedCreatePodSandBox pod/sysbox-deploy-k8s-kjrvl Failed to create pod sandbox: rpc error: code = Unknown desc = failed to get network status for pod sandbox k8s_sysbox-deploy-k8s-kjrvl_kube-system_8eddef08-5999-4875-a31e-046fe3885668_0(3da385d0f317477778f91f0740233b07f9dc5d745643f470384e4277d1be02b2): error checking pod kube-system_sysbox-deploy-k8s-kjrvl for CNI network "200-loopback.conf": cache file path requires network name (""), container ID ("3da385d0f317477778f91f0740233b07f9dc5d745643f470384e4277d1be02b2"), and interface name ("eth0")
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.
Research direction
Reproduce the failure on Azure Kubernetes 1.36.2 with a Sysbox nodepool at version 1.33.13. Start from the FailedCreatePodSandbox event and inspect the CNI "200-loopback.conf" cache error, then compare the network and nodepool configuration. Done means the Sysbox pod creates its sandbox successfully without the reported CNI error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100