-
Notifications
You must be signed in to change notification settings - Fork 79
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
test: Also wait for virt-install to finish on centos-10 #1765
Conversation
3ce6bd4
to
622317d
Compare
Aha, TF centos-10-stream is green. |
The (guessed) fix makes it reliably green: https://cockpit-logs.us-east-1.linodeobjects.com/pull-1765-67f81cd5-20240813-112925-centos-10/log.html |
67f81cd
to
3580ad1
Compare
3580ad1
to
53fad8a
Compare
53fad8a
to
4127bf5
Compare
If that works, I'm all for it! I had to make it conditional back then as waiting timed out on several OSes. I've never fully understood how Thanks! |
Yeah, what I feared -- this needs to stay conditionalized. Perhaps there's a better criterion, like the virt-install version? But for now just extending the OS list seems ok. |
Ah, I see, bummer. So the virt-install process itself sticks around forever? I have one (1) closer look and then I make this conditional. |
4127bf5
to
7f262a2
Compare
On some OSes the created VM crashes in the Maybe we should make it so that virt-install can actually produce a working VM. |
The might be the state after a "successful" installation of our fake Fedora 28 OS. So virt-install is indeed done at this point. |
Oh, the flakes... |
test/check-machines-create
Outdated
# well. (On some OSes the created VM crashes in the | ||
# kernel, on others, the BIOS can't find a bootable | ||
# device. Maybe that's the difference.) | ||
if self.create_and_run and self.machine.image in ['opensuse-tumbleweed', 'centos-10']: |
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.
I don't have proof that this affects rhel-10-0 (or not), as the last gating run in real RHEl 10 all failed due to SELinux. But it almost surely needs the same treatment. I triggered a rhel-10-0 bots run.
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.
The rhel-10-0 run confirms this. I suggest to write this as
self.machine.image.startswith(('opensuse-tumbleweed', 'centos-10', 'rhel-10'))
so that it also catches future rhel-10-* images.
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.
I have done that, and also increased the global timeout. I think opensuse runs into it.
It's unclear why.
7f262a2
to
e041f37
Compare
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.
Thanks for your investigations! The comment clarifies it a little indeed! (For our poor future selves -- this will come back and bite us in the ... a place where it hurts)
The installation is not expected to succeed, but I don't know how exactly it is expected to fail. On some OSes, a kernel is clearly started, so we must be downloading something? I think this is worth figuring out and robustifying, eventually. |
I reviewed the failures:
So in summary, I think this is fine to land, it makes things incrementally better. |
Above follow-ups: #1767 and cockpit-project/bots#6735 |
No description provided.