[Bug 1229816] New: Regression in virtualization stack
https://bugzilla.suse.com/show_bug.cgi?id=1229816 Bug ID: 1229816 Summary: Regression in virtualization stack Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Virtualization:Tools Assignee: virt-bugs@suse.de Reporter: luna.dragon@suse.com QA Contact: qa-bugs@suse.de Target Milestone: --- Found By: --- Blocker: --- We currently have some issues with the upstream cockpit test suit. When the projected attempted to update to the latest virtualization stack on tumbleweed the cockpit-machines test suite had multiple failures. If someone could help identify the cause of the regression it would be extremely helpful. The upstream pr updating the image https://github.com/cockpit-project/bots/pull/6777 the logs for the test failures: https://cockpit-logs.us-east-1.linodeobjects.com/pull-6777-640b4d08-20240822... -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1229816 Charles Arnold <carnold@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Virtualization:Tools |Cockpit Assignee|virt-bugs@suse.de |Cockpit-bugs@suse.de -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1229816 https://bugzilla.suse.com/show_bug.cgi?id=1229816#c1 Adam Majer <amajer@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |amajer@suse.com, | |dfaggioli@suse.com, | |jfehlig@suse.com --- Comment #1 from Adam Majer <amajer@suse.com> --- Were there any "unauthorized" changes in TW that could cause these failure? Or is TW in proper state when it comes to Virtualization? These cockpit tests seem like a nice canary when it comes to state of Virtualization in TW (though I haven't dug deeper into this) PS. I've added some maintainers from libvirt and Virtualization, but I don't know who could be interested in these failures. Please adjust CC list. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1229816 Robert Simai <robert.simai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |robert.simai@suse.com -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1229816 https://bugzilla.suse.com/show_bug.cgi?id=1229816#c2 Claudio Fontana <claudio.fontana@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |claudio.fontana@suse.com --- Comment #2 from Claudio Fontana <claudio.fontana@suse.com> --- (In reply to Adam Majer from comment #1)
Were there any "unauthorized" changes in TW that could cause these failure? Or is TW in proper state when it comes to Virtualization?
These cockpit tests seem like a nice canary when it comes to state of Virtualization in TW (though I haven't dug deeper into this)
The core virtualization packages work well for me. There may be bugs of course. cockpit though is not tested by the core virt team though, rather by cockpit.
PS. I've added some maintainers from libvirt and Virtualization, but I don't know who could be interested in these failures. Please adjust CC list.
The cockpit team needs to start digging deeper into those cockpit testsuite failures, and translate them to actual bug reports to the specific components as needed. Thanks, Claudio -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1229816 https://bugzilla.suse.com/show_bug.cgi?id=1229816#c3 Antoine Ginies <aginies@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aginies@suse.com --- Comment #3 from Antoine Ginies <aginies@suse.com> --- Does cockpit machine requires a specific libvirt version? Libvirt is trying to keep as much as possible retro compatibility, and if there is some removal there is an announcement. Moreover the log you provide is clearly unreadable for someone who is not familiar with this kind of layout. There is so many info on this page, this is very confusing. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1229816 https://bugzilla.suse.com/show_bug.cgi?id=1229816#c4 --- Comment #4 from Antoine Ginies <aginies@suse.com> --- I found one: "error: unsupported configuration: internal snapshot for disk vda unsupported for storage type raw" You can not do snapshot with raw image, you need to store them into a qed or qcow2 image. I think this code in cockpit machine is not doing the right testing for some of the bugs reported there. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1229816 Antoine Ginies <aginies@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1229816 Antoine Ginies <aginies@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Regression in |issue with latest cockpit |virtualization stack |machine and libvirt -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1229816 https://bugzilla.suse.com/show_bug.cgi?id=1229816#c5 --- Comment #5 from Luna D Dragon <luna.dragon@suse.com> ---
Does cockpit machine requires a specific libvirt version? Libvirt is trying to keep as much as possible retro compatibility, and if there is some removal there is an announcement.
cockpit doesn't require a specific version of libvirt. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1229816 https://bugzilla.suse.com/show_bug.cgi?id=1229816#c6 --- Comment #6 from Claudio Fontana <claudio.fontana@suse.com> --- (In reply to Luna D Dragon from comment #5)
Does cockpit machine requires a specific libvirt version? Libvirt is trying to keep as much as possible retro compatibility, and if there is some removal there is an announcement.
cockpit doesn't require a specific version of libvirt.
libvirt in tumbleweed is fairly bleeding edge. What you seem to be doing is rebasing on top of latest libvirt and finding errors in your testsuite. Most likely, upstream cockpit where these tests are developed is using an older version of libvirt, so you are the first ones finding problems. You will have to dig deeper, learn more about the interaction between components, and report the actual issues to the relevant project. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠suse.com