[BUG] Pods been deleted from gang.Children when recreated with same name.

[KunWuLuan]

What happened:

In my environment, a pod in gang may be recreated with same name. Pod add event came before pod delete event, which cause this pod is deleted from gang.Children. This can result in "No enough children in gang" and no pods can get scheduled.

What you expected to happen:

gang.Children can be set correctly when pod event came in wrong sequence.

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:

[KunWuLuan]

We can record pod uid when calling GetId() to get podId, so that pod events sequence will be handled correctly.

[ZiMengSheng]

Nice Suggestion! Could you add the detail about why pod event disordered.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, the issue is closed You can:
• Mark this issue or PR as fresh with /remove-lifecycle stale
• Close this issue or PR with /close Thank you for your contributions.