[BUG] leaky resources in ReservationInfo when pod failed to bind

[eahydra]

What happened:

1. create reservation reserves some resources.
2. create pod to allocate resources from the reservation.
3. we do some mistake to guaranteed the scheduler failed to bind, and just once mistake.
4. delete the pod.
5. create another one pod to allocate resources from the reservation.
6. failed to allocate.

What you expected to happen:

1. Pod binding the reservation, and scheduled successfully.

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

Anything else we need to know?:

Environment:

• App version:
• Kubernetes version (use kubectl version):
• Install details (e.g. helm install args):
• Node environment (for koordlet/runtime-proxy issue):
  • Containerd/Docker version:
  • OS version:
  • Kernal version:
  • Cgroup driver: cgroupfs/systemd
• Others: