April 2021 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1180754] [Build 20210110] Upgrade of any Leap 42.x to TW not possible to start
by bugzilla_noreply＠suse.com 02 Apr '21

02 Apr '21

https://bugzilla.suse.com/show_bug.cgi?id=1180754 https://bugzilla.suse.com/show_bug.cgi?id=1180754#c9 --- Comment #9 from Oliver Kurz <okurz(a)suse.com> --- This is an autogenerated message for openQA integration by the openqa_review script: This bug is still referenced in a failing openQA test: kde_live_upgrade_leap_42.3@64bit-2G https://openqa.opensuse.org/tests/1686732 To prevent further reminder comments one of the following options should be followed: 1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted 2. The openQA job group is moved to "Released" 3. The label in the openQA scenario is removed -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1182885] libvirt NodeDeviceDetach no longer works on Xen unless driver explicitly specified
by bugzilla_noreply＠suse.com 02 Apr '21

02 Apr '21

https://bugzilla.suse.com/show_bug.cgi?id=1182885 https://bugzilla.suse.com/show_bug.cgi?id=1182885#c4 James Fehlig <jfehlig(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |FIXED --- Comment #4 from James Fehlig <jfehlig(a)suse.com> --- Fix already accepted in Factory and SLE15 SP3. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1183717] u-boot fails to read btrfs
by bugzilla_noreply＠suse.com 01 Apr '21

01 Apr '21

https://bugzilla.suse.com/show_bug.cgi?id=1183717 https://bugzilla.suse.com/show_bug.cgi?id=1183717#c5 Wenruo Qu <wqu(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |matwey.kornilov(a)gmail.com Flags| |needinfo?(matwey.kornilov@g | |mail.com) --- Comment #5 from Wenruo Qu <wqu(a)suse.com> --- Would you please provide the "btrfs ins dump-tree <device>" out put of your fs? It may be a little large, but it contains all the needed info for us to debug. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1183767] New: libvirt segfault in qemuDomainDefAddDefaultDevices when invoked via vagrant
by bugzilla_noreply＠suse.com 01 Apr '21

01 Apr '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1183767 Bug ID: 1183767 Summary: libvirt segfault in qemuDomainDefAddDefaultDevices when invoked via vagrant Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Virtualization:Other Assignee: virt-bugs(a)suse.de Reporter: dcermak(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 847447 --> http://bugzilla.opensuse.org/attachment.cgi?id=847447&action=edit libvirt coredump recorded by systemd-coredump libvirt recently started segfaulting on my Leap 15.2 CI machine in openstack when a new VM is started via vagrant & vagrant libvirt. How to reproduce: - vagrant init opensuse/Tumbleweed.x86_64 # the actual vagrant box does not appear to matter - vagrant up --provider libvirt - check the system journal for a segfault installed components: $ rpm -qa|grep libvirt libvirt-libs-6.0.0-lp152.9.6.2.x86_64 libvirt-daemon-driver-network-6.0.0-lp152.9.6.2.x86_64 libvirt-daemon-driver-storage-scsi-6.0.0-lp152.9.6.2.x86_64 libvirt-daemon-driver-storage-6.0.0-lp152.9.6.2.x86_64 ruby2.5-rubygem-ruby-libvirt-0.7.1-lp152.11.1.x86_64 libvirt-daemon-6.0.0-lp152.9.6.2.x86_64 libvirt-daemon-driver-storage-gluster-6.0.0-lp152.9.6.2.x86_64 libvirt-6.0.0-lp152.9.6.2.x86_64 libvirt-daemon-driver-interface-6.0.0-lp152.9.6.2.x86_64 libvirt-daemon-driver-storage-core-6.0.0-lp152.9.6.2.x86_64 libvirt-daemon-driver-storage-disk-6.0.0-lp152.9.6.2.x86_64 ruby2.5-rubygem-fog-libvirt-0.8.0-lp152.9.1.x86_64 libvirt-daemon-driver-nodedev-6.0.0-lp152.9.6.2.x86_64 libvirt-daemon-driver-secret-6.0.0-lp152.9.6.2.x86_64 libvirt-daemon-driver-storage-logical-6.0.0-lp152.9.6.2.x86_64 libvirt-daemon-config-nwfilter-6.0.0-lp152.9.6.2.x86_64 libvirt-daemon-driver-qemu-debuginfo-6.0.0-lp152.9.6.2.x86_64 libvirt-libs-debuginfo-6.0.0-lp152.9.6.2.x86_64 libvirt-client-6.0.0-lp152.9.6.2.x86_64 libvirt-daemon-driver-libxl-6.0.0-lp152.9.6.2.x86_64 libvirt-daemon-debuginfo-6.0.0-lp152.9.6.2.x86_64 libvirt-daemon-driver-nwfilter-6.0.0-lp152.9.6.2.x86_64 libvirt-daemon-driver-storage-iscsi-6.0.0-lp152.9.6.2.x86_64 vagrant-libvirt-0.2.1-lp152.32.3.x86_64 libvirt-daemon-driver-qemu-6.0.0-lp152.9.6.2.x86_64 libvirt-daemon-config-network-6.0.0-lp152.9.6.2.x86_64 libvirt-daemon-driver-storage-rbd-6.0.0-lp152.9.6.2.x86_64 libvirt-daemon-driver-lxc-6.0.0-lp152.9.6.2.x86_64 libvirt-daemon-driver-storage-mpath-6.0.0-lp152.9.6.2.x86_64 The journal contains the following stack trace(s): Mar 19 09:16:30 dcermak-vagrant-tester-leap kernel: libvirtd[2331]: segfault at 0 ip 00007fcf90a8be2c sp 00007fcfc67fb810 error 4 in libvirt_driver_qemu.so[7fcf909f3000+19f000] Mar 19 09:16:30 dcermak-vagrant-tester-leap kernel: Code: 00 f3 a6 0f 97 c0 1c 00 84 c0 0f 94 45 90 45 31 f6 e9 95 fe ff ff 49 8b b4 24 18 02 00 00 48 8d 3d 0b 6b 0a 00 b9 06 00 00 00 <f3> a6 0f 97 c0 1c 00 84 c0 0f 84 44 ff ff ff 4c 89 e7 e8 2d fc fa Mar 19 09:16:30 dcermak-vagrant-tester-leap systemd[1]: Started Process Core Dump (PID 5268/UID 0). Mar 19 09:16:31 dcermak-vagrant-tester-leap systemd[1]: libvirtd.service: Main process exited, code=killed, status=11/SEGV Mar 19 09:16:31 dcermak-vagrant-tester-leap systemd[1]: libvirtd.service: Unit entered failed state. Mar 19 09:16:31 dcermak-vagrant-tester-leap systemd[1]: libvirtd.service: Failed with result 'signal'. Mar 19 09:16:31 dcermak-vagrant-tester-leap systemd[1]: libvirtd.service: Service RestartSec=100ms expired, scheduling restart. Mar 19 09:16:31 dcermak-vagrant-tester-leap systemd[1]: Stopped Virtualization daemon. Mar 19 09:16:31 dcermak-vagrant-tester-leap systemd[1]: Starting Virtualization daemon... Mar 19 09:16:31 dcermak-vagrant-tester-leap systemd[1]: Started Virtualization daemon. Mar 19 09:04:02 dcermak-vagrant-tester-leap systemd-coredump[1912]: Process 1767 (libvirtd) of user 0 dumped core. Stack trace of thread 1777: #0 0x00007f10dc546e2c qemuDomainDefAddDefaultDevices (libvirt_driver_qemu.so) #1 0x00007f111157fc99 virDomainDefPostParse (libvirt.so.0) #2 0x00007f111159bf08 virDomainDefParseNode (libvirt.so.0) #3 0x00007f111159c013 virDomainDefParse (libvirt.so.0) #4 0x00007f10dc5bdfbe qemuDomainDefineXMLFlags (libvirt_driver_qemu.so) #5 0x00007f11116eabbc virDomainDefineXMLFlags (libvirt.so.0) #6 0x000055572f7472ea remoteDispatchDomainDefineXMLFlags (libvirtd) #7 0x00007f111161b9ed virNetServerProgramDispatchCall (libvirt.so.0) #8 0x00007f1111620a98 virNetServerProcessMsg (libvirt.so.0) #9 0x00007f111153c751 virThreadPoolWorker (libvirt.so.0) #10 0x00007f111153bb58 virThreadHelper (libvirt.so.0) #11 0x00007f11108144f9 start_thread (libpthread.so.0) #12 0x00007f111054cecf __clone (libc.so.6) Stack trace of thread 1770: #0 0x00007f111081a87d pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0) #1 0x00007f111153bd96 virCondWait (libvirt.so.0) #2 0x00007f111153c863 virThreadPoolWorker (libvirt.so.0) #3 0x00007f111153bb58 virThreadHelper (libvirt.so.0) #4 0x00007f11108144f9 start_thread (libpthread.so.0) #5 0x00007f111054cecf __clone (libc.so.6) Stack trace of thread 1786: #0 0x00007f111081a87d pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0) #1 0x00007f111153bd96 virCondWait (libvirt.so.0) #2 0x00007f111153c863 virThreadPoolWorker (libvirt.so.0) #3 0x00007f111153bb58 virThreadHelper (libvirt.so.0) #4 0x00007f11108144f9 start_thread (libpthread.so.0) #5 0x00007f111054cecf __clone (libc.so.6) Stack trace of thread 1773: #0 0x00007f111081a87d pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0) #1 0x00007f111153bd96 virCondWait (libvirt.so.0) #2 0x00007f111153c863 virThreadPoolWorker (libvirt.so.0) #3 0x00007f111153bb58 virThreadHelper (libvirt.so.0) #4 0x00007f11108144f9 start_thread (libpthread.so.0) #5 0x00007f111054cecf __clone (libc.so.6) Stack trace of thread 1775: #0 0x00007f111081a87d pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0) #1 0x00007f111153bd96 virCondWait (libvirt.so.0) #2 0x00007f111153c798 virThreadPoolWorker (libvirt.so.0) #3 0x00007f111153bb58 virThreadHelper (libvirt.so.0) #4 0x00007f11108144f9 start_thread (libpthread.so.0) #5 0x00007f111054cecf __clone (libc.so.6) Stack trace of thread 1783: #0 0x00007f111081a87d pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0) #1 0x00007f111153bd96 virCondWait (libvirt.so.0) #2 0x00007f111153c863 virThreadPoolWorker (libvirt.so.0) #3 0x00007f111153bb58 virThreadHelper (libvirt.so.0) #4 0x00007f11108144f9 start_thread (libpthread.so.0) #5 0x00007f111054cecf __clone (libc.so.6) Stack trace of thread 1774: #0 0x00007f111081a87d pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0) #1 0x00007f111153bd96 virCondWait (libvirt.so.0) #2 0x00007f111153c798 virThreadPoolWorker (libvirt.so.0) #3 0x00007f111153bb58 virThreadHelper (libvirt.so.0) #4 0x00007f11108144f9 start_thread (libpthread.so.0) #5 0x00007f111054cecf __clone (libc.so.6) Stack trace of thread 1785: #0 0x00007f111081a87d pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0) #1 0x00007f111153bd96 virCondWait (libvirt.so.0) #2 0x00007f111153c863 virThreadPoolWorker (libvirt.so.0) #3 0x00007f111153bb58 virThreadHelper (libvirt.so.0) #4 0x00007f11108144f9 start_thread (libpthread.so.0) #5 0x00007f111054cecf __clone (libc.so.6) Stack trace of thread 1793: #0 0x00007f111081a87d pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0) #1 0x00007f111153bd96 virCondWait (libvirt.so.0) #2 0x00007f10deec3894 n/a (libvirt_driver_nodedev.so) #3 0x00007f111153bb82 virThreadHelper (libvirt.so.0) #4 0x00007f11108144f9 start_thread (libpthread.so.0) #5 0x00007f111054cecf __clone (libc.so.6) Stack trace of thread 1778: #0 0x00007f111081a87d pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0) #1 0x00007f111153bd96 virCondWait (libvirt.so.0) #2 0x00007f111153c798 virThreadPoolWorker (libvirt.so.0) #3 0x00007f111153bb58 virThreadHelper (libvirt.so.0) #4 0x00007f11108144f9 start_thread (libpthread.so.0) #5 0x00007f111054cecf __clone (libc.so.6) Stack trace of thread 1772: #0 0x00007f111081a87d pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0) #1 0x00007f111153bd96 virCondWait (libvirt.so.0) #2 0x00007f111153c863 virThreadPoolWorker (libvirt.so.0) #3 0x00007f111153bb58 virThreadHelper (libvirt.so.0) #4 0x00007f11108144f9 start_thread (libpthread.so.0) #5 0x00007f111054cecf __clone (libc.so.6) Stack trace of thread 1771: #0 0x00007f111081a87d pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0) #1 0x00007f111153bd96 virCondWait (libvirt.so.0) #2 0x00007f111153c863 virThreadPoolWorker (libvirt.so.0) #3 0x00007f111153bb58 virThreadHelper (libvirt.so.0) #4 0x00007f11108144f9 start_thread (libpthread.so.0) #5 0x00007f111054cecf __clone (libc.so.6) Stack trace of thread 1769: #0 0x00007f111081a87d pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0) #1 0x00007f111153bd96 virCondWait (libvirt.so.0) #2 0x00007f111153c863 virThreadPoolWorker (libvirt.so.0) #3 0x00007f111153bb58 virThreadHelper (libvirt.so.0) #4 0x00007f11108144f9 start_thread (libpthread.so.0) #5 0x00007f111054cecf __clone (libc.so.6) Stack trace of thread 1776: #0 0x00007f111081a87d pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0) #1 0x00007f111153bd96 virCondWait (libvirt.so.0) #2 0x00007f111153c798 virThreadPoolWorker (libvirt.so.0) #3 0x00007f111153bb58 virThreadHelper (libvirt.so.0) #4 0x00007f11108144f9 start_thread (libpthread.so.0) #5 0x00007f111054cecf __clone (libc.so.6) Stack trace of thread 1767: #0 0x00007f11105425fb __poll (libc.so.6) #1 0x00007f11114de24a poll (libvirt.so.0) #2 0x00007f11114dce01 virEventRunDefaultImpl (libvirt.so.0) #3 0x00007f11116202cd virNetDaemonRun (libvirt.so.0) #4 0x000055572f73b862 main (libvirtd) #5 0x00007f111047534a __libc_start_main (libc.so.6) #6 0x000055572f73bb3a _start (libvirtd) Stack trace of thread 1787: #0 0x00007f111081a87d pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0) #1 0x00007f111153bd96 virCondWait (libvirt.so.0) #2 0x00007f111153c863 virThreadPoolWorker (libvirt.so.0) #3 0x00007f111153bb58 virThreadHelper (libvirt.so.0) #4 0x00007f11108144f9 start_thread (libpthread.so.0) #5 0x00007f111054cecf __clone (libc.so.6) Stack trace of thread 1784: #0 0x00007f111081a87d pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0) #1 0x00007f111153bd96 virCondWait (libvirt.so.0) #2 0x00007f111153c863 virThreadPoolWorker (libvirt.so.0) #3 0x00007f111153bb58 virThreadHelper (libvirt.so.0) #4 0x00007f11108144f9 start_thread (libpthread.so.0) #5 0x00007f111054cecf __clone (libc.so.6) -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1178488] meta+e shortcut starts Dolphin as root, no pw asked
by bugzilla_noreply＠suse.com 01 Apr '21

01 Apr '21

https://bugzilla.suse.com/show_bug.cgi?id=1178488 https://bugzilla.suse.com/show_bug.cgi?id=1178488#c12 --- Comment #12 from Swamp Workflow Management <swamp(a)suse.de> --- openSUSE-RU-2021:0492-1: An update that has one recommended fix can now be installed. Category: recommended (moderate) Bug References: 1178488 CVE References: JIRA References: Sources used: openSUSE Leap 15.2 (src): kglobalaccel-5.71.0-lp152.2.6.1 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1183837] New: Boot delay due to NetworkManager-wait-online.service
by bugzilla_noreply＠suse.com 01 Apr '21

01 Apr '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1183837 Bug ID: 1183837 Summary: Boot delay due to NetworkManager-wait-online.service Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: fkrueger(a)mailbox.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Since the update to TW20210318 I am observing a boot delay of around 7 sec. for userspace due to NetworkManager-wait-online.service. As a matter of fact, > systemd-analyze blame 7.067s NetworkManager-wait-online.service 1.638s dracut-initqueue.service 727ms display-manager.service 528ms tlp.service 443ms mcelog.service 353ms initrd-switch-root.service 329ms firewalld.service 285ms postfix.service 208ms upower.service 206ms plymouth-quit-wait.service 184ms lm_sensors.service 182ms user(a)1000.service 114ms initrd-parse-etc.service 113ms home.mount 109ms udisks2.service [...] Reverting the package open-iscsi to version 2.1.3 solves the issue (thanks to Aaron Puchert for drawing my attention to iscsi.service). -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1182517] man-pages-pl incorrectly ships free.1 manpage
by bugzilla_noreply＠suse.com 01 Apr '21

01 Apr '21

https://bugzilla.suse.com/show_bug.cgi?id=1182517 https://bugzilla.suse.com/show_bug.cgi?id=1182517#c5 Antoine Belvire <antoine.belvire(a)opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |FIXED --- Comment #5 from Antoine Belvire <antoine.belvire(a)opensuse.org> --- Resolved fixed in 20210330. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1183727] Shutdown hangs frequently in various places.
by bugzilla_noreply＠suse.com 01 Apr '21

01 Apr '21

https://bugzilla.suse.com/show_bug.cgi?id=1183727 https://bugzilla.suse.com/show_bug.cgi?id=1183727#c7 --- Comment #7 from Franck Bui <fbui(a)suse.com> --- (In reply to John Carrick Smith from comment #6) > as it is the most frequent. I have attached the section of /var/log/messages > from the initiation of shutdown until the next boot in file shutdownmessages > attached. > On this occasion the shutdown hung for 90s then completed. Well can you use instead journalctl when providing the logs ? it's more reliable especially when you need to inspect the log from the shutdown process. From the logs you provided I can't see any interesting info. So can you try to reproduce your problem with the debug logs enabled (run `systemd-analyze set-log-level debug` before rebooting). When you managed to reproduce the hang please provide the output of `journalctl -b -1` which should show the log from the previous boot when the hang happened. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1183727] Shutdown hangs frequently in various places.
by bugzilla_noreply＠suse.com 01 Apr '21

01 Apr '21

https://bugzilla.suse.com/show_bug.cgi?id=1183727 https://bugzilla.suse.com/show_bug.cgi?id=1183727#c6 John Carrick Smith <jcarricksmith(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(jcarricksmith@gma | |il.com) | --- Comment #6 from John Carrick Smith <jcarricksmith(a)gmail.com> --- Created attachment 847928 --> https://bugzilla.suse.com/attachment.cgi?id=847928&action=edit Additional information as requested If you would please address the hang after the message "Stopped Name Service Cache Daemon" as it is the most frequent. I have attached the section of /var/log/messages from the initiation of shutdown until the next boot in file shutdownmessages attached. On this occasion the shutdown hung for 90s then completed. John -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1181334] wireguard-tools: support tunnel config reload
by bugzilla_noreply＠suse.com 01 Apr '21

01 Apr '21

https://bugzilla.suse.com/show_bug.cgi?id=1181334 https://bugzilla.suse.com/show_bug.cgi?id=1181334#c3 --- Comment #3 from Swamp Workflow Management <swamp(a)suse.de> --- SUSE-RU-2021:1002-1: An update that has one recommended fix can now be installed. Category: recommended (low) Bug References: 1181334 CVE References: JIRA References: Sources used: SUSE Linux Enterprise Module for Basesystem 15-SP2 (src): wireguard-tools-1.0.20200827-5.6.5 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are on the CC list for the bug.

1 0