-
Notifications
You must be signed in to change notification settings - Fork 122
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
Creation of VMs is never checked or waited for #1420
Comments
/triage accepted |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with /lifecycle stale |
/remove-lifecycle stale |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with /lifecycle stale |
/remove-lifecycle stale |
/lifecycle frozen |
The failure described here (randomly failing BMH at the end of 04 is the most common failure right now), so this would be awesome to get done. /help |
@tuminoid: Please ensure the request meets the requirements listed here. If this request no longer meets these requirements, the label can be removed In response to this:
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. |
Currently in Centos e2e, the VMs are not created so BMH cannot be inspected nor serial logs fetched etc. It seems we never check if those VMs are created, running, or healthy; we just assume they are. This makes debugging issues harder as we go all the way until end of
04_verify.sh
to find out BMH inspection fails, which could of course be happening for any reason.At the start of 04, verify the VMs are running and healthy.
/kind bug
The text was updated successfully, but these errors were encountered: