September 2021 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1184924] [Build 134.3] openQA test fails in kdump_and_crash - forced crash didn't result into expected reboot
by bugzilla_noreply＠suse.com 28 Sep '21

28 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1184924 https://bugzilla.suse.com/show_bug.cgi?id=1184924#c15 --- Comment #15 from Fabian Vogt <fvogt(a)suse.com> --- > [ 0.000000] Call trace: > [ 0.000000] kthread_should_stop+0x2c/0x60 > [ 0.000000] add_bootloader_randomness+0x2c/0x38 > [ 0.000000] efi_config_parse_tables+0x120/0x250 > [ 0.000000] efi_init+0x138/0x1e0 > [ 0.000000] setup_arch+0x394/0x778 > [ 0.000000] start_kernel+0x90/0x568 This is called only in the case that crng_init != 0. This is indeed the case, because earlier it prints: > [ 0.000000] random: fast init done My theory is that in the kexec case, there is additional entropy available through the rng-seed property in the device tree passed by the previous kernel, so the pool is already initialized when grabbing entropy through EFI. This issue does not appear on Tumbleweed (FWICT), question is which commit(s) fixed it. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1190933] New: [Build 20210926] Network: newly added interface has no name
by bugzilla_noreply＠suse.com 28 Sep '21

28 Sep '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1190933 Bug ID: 1190933 Summary: [Build 20210926] Network: newly added interface has no name Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/1940430/modules/yast 2_lan_device_settings/steps/41 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: dimstar(a)opensuse.org QA Contact: jsrain(a)suse.com Found By: openQA Blocker: Yes ## Observation openQA test in scenario opensuse-Tumbleweed-JeOS-for-kvm-and-xen-x86_64-jeos-extra@64bit_virtio-2G fails in [yast2_lan_device_settings](https://openqa.opensuse.org/tests/1940430/module… The VLAN interface has freshly been added, but has no visible name. Snapsho 0926 changed from yast2-network 4.4.23 to 4.4.25 ## Test suite description Same as jeos, plus some more tests. ## Reproducible Fails since (at least) Build [20210824](https://openqa.opensuse.org/tests/1885703) ## Expected result Last good: [20210823](https://openqa.opensuse.org/tests/1884770) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=opensus… -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1190915] New: [Build 20210926] openQA test fails in yast2_lan
by bugzilla_noreply＠suse.com 28 Sep '21

28 Sep '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1190915 Bug ID: 1190915 Summary: [Build 20210926] openQA test fails in yast2_lan Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/1940439/modules/yast 2_lan/steps/14 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: dimstar(a)opensuse.org QA Contact: jsrain(a)suse.com Found By: openQA Blocker: Yes ## Observation openQA test in scenario opensuse-Tumbleweed-GNOME-Live-x86_64-gnome-live@USBboot_64 fails in [yast2_lan](https://openqa.opensuse.org/tests/1940439/modules/yast2_lan/step… 2021-09-27 02:40:42 <3> susetest(3440) [Ruby] yast/wfm.rb(handle_exception):272 Client /usr/share/YaST2/clients/lan.rb failed with 'undefined method `description' for nil:NilClass' (NoMethodError). ## Test suite description Maintainer: dimstar(a)opensuse.org Test for openSUSE GNOME Next Live-Media EXCLUDE_MODULES is a workaround for https://bugzilla.opensuse.org/show_bug.cgi?id=1138401#c10 (except for opensuse_welcome, which is blacklisted on the GNOME live for space reasons) ## Reproducible Fails since (at least) Build [20210926](https://openqa.opensuse.org/tests/1940439) (current job) ## Expected result Last good: [20210925](https://openqa.opensuse.org/tests/1939702) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=opensus… -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1160707] New: qemu VNC console corruption
by bugzilla_noreply＠novell.com 28 Sep '21

28 Sep '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1160707 Bug ID: 1160707 Summary: qemu VNC console corruption Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: aarch64 URL: https://openqa.suse.de/tests/3773959/modules/update_ke rnel/steps/6 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Virtualization:Other Assignee: virt-bugs(a)suse.de Reporter: okurz(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- ## Observation openQA test in scenario sle-12-SP4-Server-DVD-Incidents-Kernel-aarch64-install_ltp+sle+Server-DVD-Incidents-Kernel@aarch64-virtio fails in [update_kernel](https://openqa.suse.de/tests/3773959/modules/update_kernel/steps/6) as a random problem sometimes appears on aarch64 test machines where the VM screen isn't properly cleared after boot and console output gets drawn over remnants of boot splash screen. Then the job fails because needles don't match. The problem appears less than once a week and job restart usually fixes it but it might be worth investigating further. ## Reproducible Sporadic ## Expected result Last good: [4.12.14-449.1.g4163e5c](https://openqa.suse.de/tests/3768894) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.suse.de/tests/latest?arch=aarch64&distri=sle&flavor=Server-DVD-Incidents-Kernel&machine=aarch64-virtio&test=install_ltp%2Bsle%2BServer-DVD-Incidents-Kernel&version=12-SP4) The problem appears on the osd (openqa.suse.de) aarch64 workers. OS is openSUSE Leap 15.1, qemu package versions: ``` $ sudo rpm -qa | grep qemu qemu-seabios-1.12.0-lp151.7.9.1.noarch qemu-arm-3.1.1.1-lp151.7.9.1.aarch64 qemu-ui-gtk-3.1.1.1-lp151.7.9.1.aarch64 qemu-ovmf-x86_64-0.1+svn17700-3.2.noarch qemu-3.1.1.1-lp151.7.9.1.aarch64 qemu-ipxe-1.0.0+-lp151.7.9.1.noarch qemu-block-rbd-3.1.1.1-lp151.7.9.1.aarch64 qemu-block-curl-3.1.1.1-lp151.7.9.1.aarch64 qemu-sgabios-8-lp151.7.9.1.noarch qemu-ui-sdl-3.1.1.1-lp151.7.9.1.aarch64 qemu-uefi-aarch64-2017+git1510945757.b2662641d5-lp151.10.1.noarch qemu-ui-curses-3.1.1.1-lp151.7.9.1.aarch64 qemu-ksm-3.1.1.1-lp151.7.9.1.aarch64 qemu-vgabios-1.12.0-lp151.7.9.1.noarch qemu-x86-3.1.1.1-lp151.7.9.1.aarch64 qemu-tools-3.1.1.1-lp151.7.9.1.aarch64 ``` ## Workaround Retrigger tests with new qemu instances -- You are receiving this mail because: You are on the CC list for the bug.

2 8

[Bug 1186822] glusterfs is incompatible with Transactional Server
by bugzilla_noreply＠suse.com 28 Sep '21

28 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1186822 https://bugzilla.suse.com/show_bug.cgi?id=1186822#c1 Claudio Fontana <claudio.fontana(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |claudio.fontana(a)suse.com, | |jeffm(a)suse.com Flags| |needinfo?(jeffm(a)suse.com) --- Comment #1 from Claudio Fontana <claudio.fontana(a)suse.com> --- assignee seems wrong currently. Glusterfs is opensuse-only, Jeff what do you think, who should be the assignee for this OpenSUSE bug? Thanks, CLaudio -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1190925] [Build 20210926] openQA test fails in install_ltp
by bugzilla_noreply＠suse.com 28 Sep '21

28 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1190925 https://bugzilla.suse.com/show_bug.cgi?id=1190925#c1 Fabian Vogt <fvogt(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |fvogt(a)suse.com Resolution|--- |INVALID --- Comment #1 from Fabian Vogt <fvogt(a)suse.com> --- This is https://progress.opensuse.org/issues/93237 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1190670] [Build 20210917][glibc2.34] docker blocks clone3 syscall
by bugzilla_noreply＠suse.com 28 Sep '21

28 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1190670 https://bugzilla.suse.com/show_bug.cgi?id=1190670#c12 Fabian Vogt <fvogt(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |william.brown(a)suse.com --- Comment #12 from Fabian Vogt <fvogt(a)suse.com> --- *** Bug 1190985 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1190985] Updates break zypper in docker - what(): Operation not permitted
by bugzilla_noreply＠suse.com 28 Sep '21

28 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1190985 https://bugzilla.suse.com/show_bug.cgi?id=1190985#c1 Fabian Vogt <fvogt(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |fvogt(a)suse.com Resolution|--- |DUPLICATE --- Comment #1 from Fabian Vogt <fvogt(a)suse.com> --- The usual glibc issue. *** This bug has been marked as a duplicate of bug 1190670 *** -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1185349] SeaMonkey: update to 2.53.7.1
by bugzilla_noreply＠suse.com 28 Sep '21

28 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1185349 Tristan Miller <psychonaut(a)nothingisreal.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |1191022 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1189845] SeaMonkey: update to 2.53.9
by bugzilla_noreply＠suse.com 28 Sep '21

28 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1189845 Tristan Miller <psychonaut(a)nothingisreal.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |1191022 -- You are receiving this mail because: You are on the CC list for the bug.

1 0