Every pg will record a Unschedulable type event fisrt no matter whether resources are enough and then schedule successfully.

[liuyuanchun11]

Description

1. duplicated condition update with Unschedulable and Scheduled, just retain one Scheduled is enough.
2. and add an extended condition to express the Unenqueueable event.
3. every pg will record a Unschedulable type event fisrt no matter whether resources are enough and then schedule successfully.

Steps to reproduce the issue

1. Create a vcjob in a cluster with sufficient resources. The vcjob is scheduled normally and is in the running state.
2. Execute "kubectl describe pg xxx", will see podgroup contains conditions that unschedulable and scheduled. 3.Execute “kubectl get events --sort-by='.metadata.creationTimestamp'”, will see warning event "job xxx unscheduler, reasion:...."

Describe the results you received and expected

expected:

1. Only one condition is used to describe podgroup scheduling.
2. No unscheduable warning event occurs in the pod group that is normally scheduled.

What version of Volcano are you using?

v1.9.0

Any other relevant information

No response

[JesseStutler]

I think it's a good issue. /cc @Monokaix

[JesseStutler]

/assign

[lowang-bh]

as for point 2, there is already an PR #3045.

[Monokaix]

as for point 2, there is already an PR #3045.

Maybe we can add a new condition type named Unenqueueable instead of a reason attached to Unschedulable.

[stale[bot]]

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!).

[hwdef]

Any progress?

[JesseStutler]

Not yet, I will record temporaily until I have time to fix it