### Background

I'm using the Smarter Device Manager to allow Kubernetes (K8s) containers access to devices available on nodes (for example, /dev/kvm). However, when the node restarts, it takes a while for the Smarter Device Manager to initialize, as a result, pods scheduled on such nodes requiring access to /dev/kvm error out with a status of `UnexpectedAdmissionError` and with the following error:

```
...
Annotations:  <none>
Status:  Failed
Reason:  UnexpectedAdmissionError
Message:  Pod was rejected: Allocate failed due to no healthy devices present; cannot allocate unhealthy devices smarter-devices/kvm, which is unexpected
```

Although, after a while, I see new pod pertaining to the job scheduled, the older pod still remains errored out and not removed.

### Kubernetes version
Client Version: v1.26.9
Kustomize Version: v4.5.7
Server Version: v1.26.11

### What did I expect to happen?
I expect that pods with status `UnexpectedAdmissionError` are removed automatically by Kubernetes.

### Steps to reproduce
- Create a job that deploys a pod needing access to device drivers (say /dev/kvm through smarter-device-manager).
- Restart the node on which this job is deployed.
- You will see that the pod pertaining to the aforementioned job doesn't get scheduled.

### OS
```
PRETTY_NAME="Ubuntu 22.04.2 LTS"
NAME="Ubuntu"
VERSION_ID="22.04"
VERSION="22.04.2 LTS (Jammy Jellyfish)"
VERSION_CODENAME=jammy
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
UBUNTU_CODENAME=jammy
Linux 5.15.0-105-generic #115-Ubuntu SMP Mon Apr 15 09:52:04 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
```
Pods that have UnexpectedAdmissionError are not automatically removed.
This is a GitHub Issue
repo:kubernetes
owner:kubernetes
Title : Pods that have UnexpectedAdmissionError are not automatically removed.
Issue date:

--- start body ---
### Background

I'm using the Smarter Device Manager to allow Kubernetes (K8s) containers access to devices available on nodes (for example, /dev/kvm). However, when the node restarts, it takes a while for the Smarter Device Manager to initialize, as a result, pods scheduled on such nodes requiring access to /dev/kvm error out with a status of `UnexpectedAdmissionError` and with the following error:

```
...
Annotations:  <none>
Status:  Failed
Reason:  UnexpectedAdmissionError
Message:  Pod was rejected: Allocate failed due to no healthy devices present; cannot allocate unhealthy devices smarter-devices/kvm, which is unexpected
```

Although, after a while, I see new pod pertaining to the job scheduled, the older pod still remains errored out and not removed.

### Kubernetes version
Client Version: v1.26.9
Kustomize Version: v4.5.7
Server Version: v1.26.11

### What did I expect to happen?
I expect that pods with status `UnexpectedAdmissionError` are removed automatically by Kubernetes.

### Steps to reproduce
- Create a job that deploys a pod needing access to device drivers (say /dev/kvm through smarter-device-manager).
- Restart the node on which this job is deployed.
- You will see that the pod pertaining to the aforementioned job doesn't get scheduled.

### OS
```
PRETTY_NAME="Ubuntu 22.04.2 LTS"
NAME="Ubuntu"
VERSION_ID="22.04"
VERSION="22.04.2 LTS (Jammy Jellyfish)"
VERSION_CODENAME=jammy
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
UBUNTU_CODENAME=jammy
Linux 5.15.0-105-generic #115-Ubuntu SMP Mon Apr 15 09:52:04 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
```
--- end body ---

None