failed to be scheduled pod's message increased explosively with large number of nodes

[lowang-bh]

What happened:

unschedulable info in pod condition is too large if there are many nodes.

kubectl get events |grep deploy-with-volcano

What you expected to happen:

should sum up same fail to be scheduled reason among multiple nodes, like this:

How to reproduce it (as minimally and precisely as possible):

1. add multiple nodes (virtual-kubelet, kwok)
2. create a deployment/vc-job scheduled by volcano
3. describe pod

Anything else we need to know?:

Environment:

• Volcano Version: master branch
• Kubernetes version (use kubectl version):
• Cloud provider or hardware configuration:
• OS (e.g. from /etc/os-release):
• Kernel (e.g. uname -a):
• Install tools:
• Others:

[lowang-bh]

similar issue about unschedulable pod's log: Optimize log output when resources are not enough #2993

[lowang-bh]

same issue as diffferent value of variable in returned err will cause event message too long #2975

Maybe it is introduced by PR #2916