User pod is not destroyed if Notebook controller is failed to spawn JL notebook

Description of problem:

When the notebook controller is failed to spawn a notebook due to fewer resources or any other reason. User pod is stuck and pending state and it is not destroyed automatically

Note: This was not observed with JH. With JH pod will be destroyed automatically.

Prerequisites (if any, like setup, operators/versions):

RHODS 1.16(1.16.0-dashboard-kfnbc )

Steps to Reproduce

1. Create a cluster
2. Install RHODS 1.16 live build
3. Launch Dashboard and launch Jupyter
4. Spawan Medium-size notebook
5. Spawn will fail due to limited resource
6. Observed that POD was not deleted

Actual results:

User pod is not destroyed if Notebook controller is failed to spawn JL notebook

Expected results:

User pod is destroyed if the Notebook controller is failed to spawn JL notebook

Reproducibility (Always/Intermittent/Only Once):

Always

Build Details:

Workaround:

Click on `close` button. it will destroy the pod

Additional info: