volcano restarts due to panic
Description
When Volcano is used for scheduling, the system restarts for multiple times.Restart cause: out-of-bounds array causes panic.
error details:
kubectl logs -f -n volcano-system volcaho-scheduler-xx -p
2024/08/27 10:47:39 maxprocs: Updating GOMAXPROCS=20: determined from CPU quota
W0827 10:47:39.514559 1 client config go:617] Neither --kubeconfig nor --master was specified. Using the inclusterConfig.s This might not work.
I0827 10:48:01.142318 1 trace.go:205] Trace[1974509093]: "Reflector ListAndWatch" name:pkg/mod/k8s.io/[email protected]/tools/cache/reflector.go:169 (27-Aug-2024 10:47:39.584)(total time: 2155
7ms):
Trace[1974509093]: ---"Objects listed" error:
goroutine 81093 [running]: k8s.io/api/core/v1.(*PodStatus).DeepCopyInto(Ox402dd59be8, 0x4019da0af8) /devcloud/slavespace/slave1-new/workspace/j_CmcZc9ms/pkg/mod/k8s.io/[email protected]/core/v1/zz generated.deepcopy.go:3982 +0x5cc kgs.io/api/core/v1.(*Pod).DeepCopyInto(Ox402dd598f0, 0x4019da0800) /devcloud/slavespace/slave1-new/workspace/j_CmcZc9ms/pkg/mod/k8s.io/[email protected]/core/v1/zz_generated.deepcopy.go:3309 +0x100 k8s.io/api/core/v1.(*Pod).DeepCopy(...) /devcloud/slavespace/slave1-new/workspace/j_CmcZc9ms/pkg/mod/k8s.io/[email protected]/core/v1/zz generated deepcopy go:3319 volcano.sh/volcano/pkg/scheduler/cache.(*defaultEvictor).Evict(0x400088e2e8, 0x402dd598f0, {0x4046557f68, 0x4}) /devcloud/slavespace/slave1-new/workspace/j_CmcZc9ms/src/volcano.sh/volcano/pkg/scheduler/cache/cache.go:209 +0x1a4 volcano.sh/volcano/pkg/scheduler/cache.(*SchedulerCache).Evict.func1() /devcloud/slavespace/slave1-new/workspace/j_CmcZc9ms/src/volcano.sh/volcano/pkg/scheduler/cache/cache.go:751 +0x44 created by volcano.sh/volcano/pkg/scheduler/cache.(*SchedulerCache).Evict /devcloud/slavespace/slave1-new/workspace/j CmcZc9ms/src/volcano.sh/volcano/pkg/scheduler/cache/cache.go:750 +0x338
Steps to reproduce the issue
Describe the results you received and expected
solve the panic problem
What version of Volcano are you using?
1.7
Any other relevant information
No response
Is this from volcano repo?
Is this from volcano repo?
yes
Did you install volcano-admission correctly?
Is this from volcano repo?
yes
You add a custom plugin?
Did you install volcano-admission correctly?
yes,and add a custom plugin
Is this from volcano repo?
yes
You add a custom plugin?
yes. I've been using the new plugin for two years. I found this problem recently.
From the picture you pasted, seems it's caused by your own plugin, maybe you can check the custom plugin first.
Hello 👋 Looks like there was no activity on this issue for last 90 days. Do you mind updating us on the status? Is this still reproducible or needed? If yes, just comment on this PR or push a commit. Thanks! 🤗 If there will be no activity for 60 days, this issue will be closed (we can always reopen an issue if we need!).
Closing for now as there was no activity for last 90 days after marked as stale, let us know if you need this to be reopened! 🤗