[Bug 1206237] New: [Build 20221207] nested_vm not showing up
http://bugzilla.opensuse.org/show_bug.cgi?id=1206237 Bug ID: 1206237 Summary: [Build 20221207] nested_vm not showing up Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/2937999/modules/nest ed_vm/steps/36 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Virtualization:Other Assignee: virt-bugs@suse.de Reporter: dimstar@opensuse.org QA Contact: qa-bugs@suse.de Found By: openQA Blocker: Yes ## Observation This is possibly a regression from libvirt update 8.9->8.10 the test launches a nested VM using virt-install --memory=512 --name=nested_vm_test --graphics=vnc --disk=none --boot=cdrom) After that, the test issues a "virsh list --all" and expects that nested_vm_test to show up there openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-upgrade_Leap_15.2_with_service_check@64bit fails in [nested_vm](https://openqa.opensuse.org/tests/2937999/modules/nested_vm/steps/36) ## Test suite description Maintainer: wegao@suse.com Upgrade test Leap 15.2 to TW with service check Currently ONLY exist libvirt service check, if more service needed we can added into it. Extra setting: NESTED_VM_DOWN=1 will shutdown nested vm before migraiton ## Reproducible Fails since (at least) Build [20221207](https://openqa.opensuse.org/tests/2936174) ## Expected result Last good: [20221206](https://openqa.opensuse.org/tests/2934162) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=opensuse&flavor=DVD&machine=64bit&test=upgrade_Leap_15.2_with_service_check&version=Tumbleweed) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1206237 Dominique Leuenberger <dimstar@opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P2 - High -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1206237 http://bugzilla.opensuse.org/show_bug.cgi?id=1206237#c1 --- Comment #1 from James Fehlig <jfehlig@suse.com> --- (In reply to Dominique Leuenberger from comment #0)
## Observation
This is possibly a regression from libvirt update 8.9->8.10
the test launches a nested VM using virt-install --memory=512 --name=nested_vm_test --graphics=vnc --disk=none --boot=cdrom)
I'm surprised this test ever worked. The same virt-install command fails on my TW host due to missing OS name # virt-install --memory=512 --name=nested_vm_test --graphics=vnc --disk=none --boot=cdrom ERROR --os-variant/--osinfo OS name is required, but no value was set or detected. This is now a fatal error. Specifying an OS name is required for modern, performant, and secure virtual machine defaults. You can see a full list of possible OS name values with: virt-install --osinfo list If your Linux distro is not listed, try one of generic values such as: linux2022, linux2020, linux2018, linux2016 If you just need to get the old behavior back, you can use: --osinfo detect=on,require=off Or export VIRTINSTALL_OSINFO_DISABLE_REQUIRE=1 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1206237 http://bugzilla.opensuse.org/show_bug.cgi?id=1206237#c2 --- Comment #2 from Dominique Leuenberger <dimstar@opensuse.org> --- Last successful run was https://openqa.opensuse.org/tests/2934162#step/nested_vm/42 (yesterday) we can see the warning about no os detected there too. but I just see that this is even weirder The test actually does: * Boot a Leap 15.2 disk image <-- I missed that before * Installs libvirtd (plus deps) * Calls those virt-install/virt-list commands So at this stage, there is really no way the Tumbleweed update could influence the failure. The test would then continue to update the 15.2 image to a TW, and perform a check if the nested_vm is still listed (so if it survived the upgrade) Now, I have to admit I have no clue (yet) why the first one inside a (not modified, and hopefully no updates published) 15.2 image would start to fail. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1206237 http://bugzilla.opensuse.org/show_bug.cgi?id=1206237#c3 --- Comment #3 from James Fehlig <jfehlig@suse.com> --- (In reply to Dominique Leuenberger from comment #2)
Last successful run was https://openqa.opensuse.org/tests/2934162#step/nested_vm/42 (yesterday)
we can see the warning about no os detected there too.
but I just see that this is even weirder
The test actually does: * Boot a Leap 15.2 disk image <-- I missed that before * Installs libvirtd (plus deps) * Calls those virt-install/virt-list commands
Ah, that explains why the virt-install command succeeds with only the warning. On TW the same command will now fail.
Now, I have to admit I have no clue (yet) why the first one inside a (not modified, and hopefully no updates published) 15.2 image would start to fail.
Agree that is very odd and inexplicable :-). -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1206237 http://bugzilla.opensuse.org/show_bug.cgi?id=1206237#c4 Dominique Leuenberger <dimstar@opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |WORKSFORME --- Comment #4 from Dominique Leuenberger <dimstar@opensuse.org> --- Today, as inexplicable as yesterday, the same test passes again https://openqa.opensuse.org/tests/2940795 (it's not as it only failed once yesterday... so the moon and starts must have been mis-aligned) let's close this -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠suse.com