-
Notifications
You must be signed in to change notification settings - Fork 17
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
New VMs: we need netavark 1.10.3 #327
Conversation
Cirrus CI build successful. Found built image names and IDs:
|
Sigh. Got .2 in rawhide, but not f39. Will try a respin later in the week.
|
bodhi has been submitted. If we need something right away, we can grab the koji build from https://koji.fedoraproject.org/koji/buildinfo?buildID=2396597 in the build. |
1bbc8e4
to
11593ef
Compare
11593ef
to
5cc0340
Compare
Cirrus CI build successful. Found built image names and IDs:
|
Yay, finally have new netavark. Testing in 17831.
|
@containers/podman-maintainers @containers/netavark-maintainers I'm really confused here. Every single fedora e2e test failed, and every single one of them in netavark tests: https://cirrus-ci.com/build/4795190137847808 (Debian failed too, but that's because of the new runc, and I'm not even going to bother looking at that today). This is a diff against the packages in the current-podman-CI VMs. I have to conclude that netavark-1.10.2 is broken:
|
That seems possible although I would not understand why it broke as the only fix was the network update issue and I see failing tests do not not call update at all. All failures seem related to dns so maybe the bug is on the aardvark-dns side. I will see if I can reproduce locally and given they failed on all tests that shouldn't be to hard. |
But aardvark-dns didn't change! (Okay, AWS, but nowhere else) |
yes it is netavark, the patch containers/netavark#912 is buggy |
Thank you for looking into it. I'm really sorry to have dumped it on you. |
Also, add "rpm -qa" (fedora) and "dpkg -l" (debian) so Ed's package-version script can get better data. It would be nice if we could save those to an artifact file, but we can't. Signed-off-by: Ed Santiago <[email protected]>
5cc0340
to
15fe970
Compare
Cirrus CI build successful. Found built image names and IDs:
|
|
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.
@cevich PTAL. VMs are already in use for podman: containers/podman#21618 so this is an FYI review, just so you're aware of the stuff that's going on here.
I am deliberately not tagging this build because there's a nasty rawhide bug that I really don't want to have to track in more repos.
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.
LGTM. Ed, there's a pair of minor things not worth rebuilding/testing for. Would you consider doing them in a [CI:DOCS]
followup PR?
Since these VMs are already in use in podman, I would hope that this can be merged. The issues you raised (adding comments re: netavark bodhi; using some variable instead of getting it myself) are timebombed and will be obsolete within 24-48 hours, so I choose not to submit a new CI:DOCS PR to address them. |
Oh sorry I didn't realize they were that quick. Np then. |
Signed-off-by: Ed Santiago [email protected]