-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
kvm2 test failures: unable to stop vm, current state "Running" #5723
Comments
Does it only happen with the crio runtime ? Maybe we are missing a systemd service here... In the repository there are three services: crio.service, crio-wipe.service, crio-shutdown.service [Unit]
Description=Shutdown CRI-O containers before shutting down the system
Wants=crio.service
After=crio.service
Documentation=man:crio(8)
[Service]
Type=oneshot
ExecStart=/usr/bin/rm -f /var/lib/crio/crio.shutdown
ExecStop=/usr/bin/bash -c "/usr/bin/mkdir /var/lib/crio; /usr/bin/touch /var/lib/crio/crio.shutdown"
RemainAfterExit=yes
[Install]
WantedBy=multi-user.target
|
@afbjorklund it seems to be a recuring one for ciro test on kvm here is another one on current Master: |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
crio test appears to be stable now on KVM:
error message appears to have slowed down in frequency, haven't seen in past week:
|
On master I have been seeing lots and lots of fails on "TestStartStop/group/crio"
as seen in this PR : https://storage.googleapis.com/minikube-builds/logs/5721/KVM_Linux.txt
here is one from master:
The text was updated successfully, but these errors were encountered: