May 2022 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1187327] [riscv64] Tumbleweed update repository does not exist
by bugzilla_noreply＠suse.com 03 May '22

03 May '22

https://bugzilla.suse.com/show_bug.cgi?id=1187327 https://bugzilla.suse.com/show_bug.cgi?id=1187327#c3 --- Comment #3 from Andreas Schwab <schwab(a)suse.de> --- No. The repository setup is borken. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1198952] VUL-0: CVE-2022-24735: redis: Lua code injection
by bugzilla_noreply＠suse.com 03 May '22

03 May '22

https://bugzilla.suse.com/show_bug.cgi?id=1198952 https://bugzilla.suse.com/show_bug.cgi?id=1198952#c3 --- Comment #3 from Danilo Spinella <danilo.spinella(a)suse.com> --- codestream | redis SUSE:SLE-15:Update | 6.0.14 SUSE:SLE-15-SP2:Update | 6.0.14 SUSE:SLE-15-SP4:Update | 6.2.6 The patch doesn't apply to 6.0.14, the codebase is too different. In addition, 6.0.x is not maintained anymore, so there is no release fixing this CVE. How should I proceed? https://github.com/redis/redis/pull/10651 For SLE-15-SP4:Update I'll open an ECO to update to 6.2.7. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1197610] [Build 20220326] accountsservice fails to start on SELinux enabled system
by bugzilla_noreply＠suse.com 03 May '22

03 May '22

https://bugzilla.suse.com/show_bug.cgi?id=1197610 https://bugzilla.suse.com/show_bug.cgi?id=1197610#c5 --- Comment #5 from Johannes Segitz <jsegitz(a)suse.com> --- The changes in the .service file cause this, specifically ReadWritePaths=\ -/etc/gdm/custom.conf \ /etc/ \ -/proc/self/loginuid \ -/var/log/lastlog \ -/var/log/tallylog \ -/var/mail/ ReadOnlyPaths=\ /usr/share/accountsservice/interfaces/ \ /usr/share/dbus-1/interfaces/ \ /var/log/wtmp \ /run/systemd/seats/ this causes the mount operations to happen -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1196862] New: [Build 20220307] OVN missing from Tumbleweed
by bugzilla_noreply＠suse.com 03 May '22

03 May '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1196862 Bug ID: 1196862 Summary: [Build 20220307] OVN missing from Tumbleweed Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/2234165/modules/ovn/ steps/19 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: screening-team-bugs(a)suse.de Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: openQA Blocker: Yes ## Observation openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-extra_tests_textmode@64bit fails in [ovn](https://openqa.opensuse.org/tests/2234165/modules/ovn/steps/19) The latest openvswitch package claimed to separate out ovn into a separate build: +- Separated OVN + * Stand alone package, this enables better maintenance + especially updates. Unfortunatley, so far, this has not been submitted for inclusion into Factory. Is still still valid? Or should we drop the test? ## Test suite description Maintainer: slindomansilla(a)suse.de. Mainly post-installation console extra tests. ## Reproducible Fails since (at least) Build [20210920](https://openqa.opensuse.org/tests/1930034) ## Expected result Last good: [20210920](https://openqa.opensuse.org/tests/1930033) (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 8

[Bug 1199145] New: upstream kernel v5.17 regresses 40-50% on aim9 benchmark
by bugzilla_noreply＠suse.com 03 May '22

03 May '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1199145 Bug ID: 1199145 Summary: upstream kernel v5.17 regresses 40-50% on aim9 benchmark Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: giovanni.gherdovich(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 858602 --> http://bugzilla.opensuse.org/attachment.cgi?id=858602&action=edit Full bisection logs The Marvin/MMTests infrastructure found the following regression in the aim9 benchmark: v5.16 v5.17 Hmean page_test 850978.70 ( 0.00%) 809251.79 * -4.90%* Hmean brk_test 5717428.87 ( 0.00%) 5695625.26 ( -0.38%) Hmean exec_test 490.90 ( 0.00%) 250.17 * -49.04%* Hmean fork_test 3359.38 ( 0.00%) 2085.48 * -37.92%* Stddev page_test 3498.99 ( 0.00%) 8324.35 (-137.91%) Stddev brk_test 70897.80 ( 0.00%) 78872.00 ( -11.25%) Stddev exec_test 18.86 ( 0.00%) 0.53 ( 97.18%) Stddev fork_test 38.24 ( 0.00%) 36.83 ( 3.68%) The regression bisects to 98b0d890220d45418cfbc5157b3382e6da5a12ab ("sched/pelt: Relax the sync of util_sum with util_avg") See the attachment for the full bisection log. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1199051] [Build 20220430] dracut - post trans failure
by bugzilla_noreply＠suse.com 03 May '22

03 May '22

https://bugzilla.suse.com/show_bug.cgi?id=1199051 https://bugzilla.suse.com/show_bug.cgi?id=1199051#c7 Antonio Feijoo <antonio.feijoo(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo? | --- Comment #7 from Antonio Feijoo <antonio.feijoo(a)suse.com> --- (In reply to Dominique Leuenberger from comment #4) > There was also tests not related to MicroOS failing, such as > https://openqa.opensuse.org/tests/2323205 In that test, the problem is related to this upstream fallback condition when the system is being installed and does not have any initrd yet: https://github.com/openSUSE/dracut/blob/SUSE/056/dracut.sh#L1089-L1092 Removing them from our openSUSE branch should solve this issue. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1152105] info vs gzip
by bugzilla_noreply＠suse.com 03 May '22

03 May '22

https://bugzilla.suse.com/show_bug.cgi?id=1152105 Marcus Meissner <meissner(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |meissner(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1198066] [Staging] yast2-ntp relies on the presence of /sbin/netconfig
by bugzilla_noreply＠suse.com 03 May '22

03 May '22

https://bugzilla.suse.com/show_bug.cgi?id=1198066 https://bugzilla.suse.com/show_bug.cgi?id=1198066#c5 Knut Alejandro Anderssen Gonz�lez <kanderssen(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mfilka(a)suse.com Flags|needinfo?(kanderssen(a)suse.c |needinfo?(mfilka(a)suse.com) |om) | --- Comment #5 from Knut Alejandro Anderssen Gonz�lez <kanderssen(a)suse.com> --- (In reply to Thorsten Kukuk from comment #4) > Big question: is netconfig really required here? > > By looking at the netconfig ntp code: it creates a new temporary NTP server > list (does it have access to all input files if it is running inside the new > system, while everything else is running in the inst-sys? Or are we have now > an incomplete list?) and updates the currently running chronyd from the > inst-sys with this list. > > 1. does this really do what is expected? > 2. why do we need to "update" the running ntp server list of the currently > running chronyd from the inst-sys at the end of the installation? > 3. why do we run something, which calls many other tools and modifies > running daemons in the inst-sys from a chroot system? Is this really safe? > > Since this all works fine without netconfig (that's really a bad documented > scripting mess) and we clearly want to move to use only native > NetworkManager (why limiting ourself and customers by having netconfig in > the middle, which means we have to re-implement and maintain all the > supporting scripts a second time at our own and miss all new upstream > features?). > > My suggestion would be: check for the existence of netconfig, and don't call > it if it does not exist. Else you have to touch the code again in a few > weeks. I completely agree, BTW mchf was checking the current state of ntp configuration since we moved to chronyd so I guess these checks could be part of his current work. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1157035] New: Xen 4.13.0 RC1, dom0 backtrace in xen_mc_flush
by bugzilla_noreply＠novell.com 03 May '22

03 May '22

http://bugzilla.suse.com/show_bug.cgi?id=1157035 Bug ID: 1157035 Summary: Xen 4.13.0 RC1, dom0 backtrace in xen_mc_flush Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Xen Assignee: xen-bugs(a)suse.de Reporter: ohering(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 824366 --> http://bugzilla.suse.com/attachment.cgi?id=824366&action=edit tw.txt A fresh TW 20191112 shows the attached backtrace in dom0 after initial boot. Only the Xenstore domU is running. [ 61.673738] WARNING: CPU: 2 PID: 1416 at arch/x86/xen/multicalls.c:102 xen_mc_flush+0x1d0/0x200 [ 61.680650] CPU: 2 PID: 1416 Comm: (agetty) Not tainted 5.3.9-1-default #1 openSUSE Tumbleweed (unreleased) [ 61.685777] Hardware name: HP ProLiant SL160z G6 /ProLiant SL160z G6 , BIOS O33 07/28/2009 -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1199051] [Build 20220430] dracut - post trans failure
by bugzilla_noreply＠suse.com 03 May '22

03 May '22

https://bugzilla.suse.com/show_bug.cgi?id=1199051 https://bugzilla.suse.com/show_bug.cgi?id=1199051#c6 --- Comment #6 from Antonio Feijoo <antonio.feijoo(a)suse.com> --- (In reply to Dominique Leuenberger from comment #4) > Also, you seem to have seen the same issue before even submitting dracut to > Factory (as per your comment in bug#1198681) No, that was not an issue. It's just to show the changes introduced that seem to cause this bug and that it's blocking its resolution. -- You are receiving this mail because: You are on the CC list for the bug.

1 0