-
Notifications
You must be signed in to change notification settings - Fork 129
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
Pass {USER, COREOS}_DATA
separately in testcloud
#3266
Conversation
768a3ca
to
732767f
Compare
aa3927b
to
98b1b23
Compare
/packit test |
{USER, COREOS}_DATA
separately in testcloud
/packit test |
520b077
to
1636374
Compare
/packit test |
2 similar comments
/packit test |
/packit test |
So, the CoreOS tests failed previously, the upcoming run has https://pagure.io/testcloud/pull-request/204 included which should resolve that too. tldr. previously, we could use sock.connect_ex(("127.0.0.1", self.get_instance_port())) in testcloud CoreOS/user sessions to verify that ssh port is open, but something had changed in how this works in libvirt/qemu, and the call now instantly returns OK. |
@psss Reading through the results, if I am not missing anything, the issues are mainly:
which wouldn't seem caused by testcloud/this PR, and fedora-coreos failures, which I have problems reproducing locally. All in all, this seems to resolve the mysterious failures at least for normal Fedora Cloud :/ |
Bumped the require again in 8f4d1db to get the regression fix. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Now seems to be working nice! 🎉
Adjust the test for now to exercise the custom command path only. Reboot timeout in testcloud's `instance.reboot()` will be handled separately.
@happz, and it's green! \o/ |
Together with now staged testcloud-0.11.0, should resolve #3235 once and for all.
Required testcloud is built at: https://copr.fedorainfracloud.org/coprs/frantisekz/testcloud-temp/
The {USER, COREOS}_DATA variables were affected by threads overwriting them directly in testcloud's config object as observed in #3244 (comment) and following comments. Testcloud-side change can be seen here: https://pagure.io/testcloud/c/ee1202bcf57cd475f4586f3693e2127f9a12e92e?branch=master .
Only these two variables can differ between various instances in tmt's use of testcloud, the others are kept separately since the domain api switchover last year: #2078 .
Co-authored by @jskladan
@happz @psss
Pull Request Checklist