You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Occasionally a job will get stuck and remain in "running" status. The target VM(s) continue to exist and who knows what they are doing. Eventually, after many hours, a cronjob will delete the VMs.
I've found that running "teuthology-kill" on these stuck jobs has essentially no effect. The job status does not change and the target VMs continue to exist.
Occasionally a job will get stuck and remain in "running" status. The target VM(s) continue to exist and who knows what they are doing. Eventually, after many hours, a cronjob will delete the VMs.
I've found that running "teuthology-kill" on these stuck jobs has essentially no effect. The job status does not change and the target VMs continue to exist.
The text was updated successfully, but these errors were encountered: