Openshift Event Code: 1038CLST0005
Summary: Pod container waiting longer than 1 hour
This article applies to
This article does not apply to
This article is not tied to any specific product.
Not all product versions are identified in this article.
Symptoms
Certain pod in certain namespace on certain container has been in waiting state for longer than 1 hour.
Cause
If a Pod is stuck in the Waiting state, then it has been scheduled to a worker node, but it can't run on that machine. Again, the information from kubectl describe ... should be informative. The most common cause of Waiting pods is a failure to pull the image.
Resolution
Diagnosis：
- Check pod events via oc -n $NAMESPACE describe pod $POD.
- Check pod logs via oc -n $NAMESPACE logs $POD -c $CONTAINER
- Check for missing files such as configmaps/secrets/volumes
- Check for pod requests, especially special ones such as GPU.
- Check for node taints and capabilities.
Mitigation：
See Container waiting
Support：
If all the above steps cannot resolve the issue, contact the Dell EMC technical support for further investigation.
Affected Products
APEX Cloud Platform for Red Hat OpenShiftArticle Properties
Article Number: 000217414
Article Type: Solution
Last Modified: 19 فبراير 2026
Version: 4
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.