PVC related e2e verification fails probabilistically

[wangyang0616]

What happened: PVC related e2e verification fails probabilistically.

What you expected to happen: e2e works stably How to reproduce it (as minimally and precisely as possible): make e2e

Anything else we need to know?:

Environment:

• Volcano Version:
• 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:

[wangyang0616]

/assign

[Mufengzhe]

When running this test case, a pv named "job-pv-name" will first be created, and then a pvc named "job-pvc-name-exist" will be created and bound to the previously created pv. Then create a job to mount two pvc, one is the "job-pvc-name-exist" created before, and the other will be created when the job is created. As expected, the first created pvc named "job-pvc-name-exist" will be bound to the pv named "job-pvc-name", and the pvc created after the job will automatically create a pv and bind it Set to this pv. Then the job is created normally and the test passes. But in practice, we found that the pvc created with the job will preemptively bind to the already created pv, causing the existing pvc to be unable to be bound to "job-pv-name", so it has always been in In Pending state, the job cannot be started normally, and the final test fails. But after installing the volcano environment, when running the test case through ginkgo alone, it will pass the test successfully according to the expected effect. that is so weird