Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The test job has been stuck in a pending state and cannot be terminated. #34472

Open
HirazawaUi opened this issue Mar 9, 2025 · 2 comments
Open
Labels
kind/bug Categorizes issue or PR as related to a bug. needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one.

Comments

@HirazawaUi
Copy link
Contributor

What happened:
The test job has been stuck in a pending state and cannot be terminated.

What you expected to happen:
The test job can terminate normally, reporting either success or failure.

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

Please provide links to example occurrences, if any:
I discovered this issue in kubernetes/kubernetes#127122, where two jobs have been stuck in pending state and cannot be marked as either successful or failed.

Test job details page: https://prow.k8s.io/view/gs/kubernetes-ci-logs/pr-logs/pull/127122/pull-kubernetes-conformance-kind-ipv6-parallel/1898020412499955712

In the build logs, I saw the following error output:

+ kind delete cluster
Deleting cluster "kind" ...
ERROR: failed to delete cluster "kind": failed to delete nodes: command "docker rm -f -v kind-worker kind-control-plane kind-worker2" failed with error: exit status 1

This indicates that Kind was unable to properly tear down the nodes, which might be the reason why the job cannot terminate normally.

I’m not sure if this is the best place to report this issue. If it isn’t, please let me know, and I’ll report it in the appropriate place.

Anything else we need to know?:

@HirazawaUi HirazawaUi added the kind/bug Categorizes issue or PR as related to a bug. label Mar 9, 2025
@k8s-ci-robot k8s-ci-robot added the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Mar 9, 2025
@k8s-ci-robot
Copy link
Contributor

There are no sig labels on this issue. Please add an appropriate label by using one of the following commands:

  • /sig <group-name>
  • /wg <group-name>
  • /committee <group-name>

Please see the group list for a listing of the SIGs, working groups, and committees available.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@HirazawaUi
Copy link
Contributor Author

The job eventually entered a failed state with the status: "Pod running timeout." However, this job actually ran successfully.

Ref: https://prow.k8s.io/view/gs/kubernetes-ci-logs/pr-logs/pull/127122/pull-kubernetes-conformance-kind-ipv6-parallel/1898020412499955712

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one.
Projects
None yet
Development

No branches or pull requests

2 participants