October 2021 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1190568] New: python39-base requires /usr/bin/python3
by bugzilla_noreply＠suse.com 28 May '22

28 May '22

https://bugzilla.suse.com/show_bug.cgi?id=1190568 Bug ID: 1190568 Summary: python39-base requires /usr/bin/python3 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: screening-team-bugs(a)suse.de Reporter: dcermak(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The python39-base package currently requires /usr/bin/python3, which is solely provided by python3-base (i.e. the python 3.6 version). This means that it is impossible to create a python 3.9 only system based on Leap 15.3/SLE 15 SP3. Could %bindir/python3 be please handled via alternatives or a metapackage, so that we can create containers with python 3.9 but without python 3.6? -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1190632] New: Failure to reboot guests consistently at least 100 times
by bugzilla_noreply＠suse.com 27 May '22

27 May '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1190632 Bug ID: 1190632 Summary: Failure to reboot guests consistently at least 100 times Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Virtualization:Tools Assignee: virt-bugs(a)suse.de Reporter: luis.chamberlain(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Upstream kdevops [0] has a workflow test called "reboot-limit". The goal is to spawn a guest and then reboot it and confirm each reboot at least 100 times. If that fails the test fails. On to of this, the real goal is to run this simple test 100 times, so for a full set of 10,000 reboots. This is called achieving steady state for the reboot-limit kdevops test. To spawn guests vagrant is used. Right now I'm using this to vagrant with libvirt, and so behind the scenes this is all libvirt. I've been following Tumbleweed for a while now and in all releases so far I've only been able to accomplish a successful reboot-limit test only once, and so it would seem it might just be chance. kdevops uses ansible to control guests. There are 3 simple steps to the reboot: 1) ansible reboot module will first ssh to the guest and query /proc/sys/kernel/random/boot_id and saves this random UUID. 2) Ansible will ssh to the guest and issue '/sbin/shutdown -r 0 ' to reboot the guest 3) Yet again ansible will try to loop trying to ssh to the guest for up to 600 seconds, and once it logs in it will query again /proc/sys/kernel/random/boot_id. If the UUIDs match then the reboot is determined to have failed. Now, using /proc/sys/kernel/random/boot_id does not change in containers, and so on ansible 2.10 boot_time_command was added to the reboot module to allow you to specify another check. But for guests, this should work fine. OpenSUSE Tumbleweed is running ansible-2.9.24-1.1.noarch. With this the reboot-failure can't pass more than 100 reboots easily, sometimes maybe it reaches 200 or 500 but that's it. A workaround I noticed was to use: diff --git a/playbooks/roles/reboot-limit/tasks/do-reboot.yml b/playbooks/roles/reboot-limit/tasks/do-reboot.yml index a6876d2..2841bf6 100644 --- a/playbooks/roles/reboot-limit/tasks/do-reboot.yml +++ b/playbooks/roles/reboot-limit/tasks/do-reboot.yml @@ -12,6 +12,7 @@ become: yes become_method: sudo reboot: + post_reboot_delay: 10 when: - reboot_limit_test_type == "ansible" tags: [ 'run_tests' ] I've had to merge the above fix to kdevops because otherwise this test fails easily... With this we are able to get 10,000 reboots on OpenSUSE Tumbleweed. But, on Debian testing using ansible 2.10.7 and linux-next, I'm easily able to get 1,000,0000 reboots and without the above hack. Which begs the question: where is the issue? I checked ansible with verbose (ansible-playbook -vvv) for the test and it would seem everything checks out except the timeout really happens. But the odd thing is that you are able to still ssh to the host when you go and check to see what the hell happened. Which would seem to indicate the issue might be something else. [0] https://github.com/mcgrof/kdevops -- You are receiving this mail because: You are on the CC list for the bug.

1 30

[Bug 1187654] New: MicroOS IMA enabled system, dracut-pre-privot error
by bugzilla_noreply＠suse.com 27 May '22

27 May '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1187654 Bug ID: 1187654 Summary: MicroOS IMA enabled system, dracut-pre-privot error Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: aplanas(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- In a MicroOS IMA enabled system, via de system role, the first boot shows this error: localhost dracut-pre-pivot[394]: ls: cannot access '/sysroot/etc/keys/ima/*': No such file or directory -- You are receiving this mail because: You are on the CC list for the bug.

1 11

[Bug 1191752] New: [SLPP] cluster-glue: E: shlib-policy-name-error
by bugzilla_noreply＠suse.com 27 May '22

27 May '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1191752 Bug ID: 1191752 Summary: [SLPP] cluster-glue: E: shlib-policy-name-error Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: martin.liska(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The following rpmlint error was seen for the package: cluster-glue.log:[ 112s] libglue2.x86_64: E: shlib-policy-name-error SONAME: libstonith.so.1, expected package suffix: 1 Note the updated rpmlint will reach openSUSE:Factory soon. We would like to make 'shlib-policy-name-error' a package build failure error, so please fix the error. Link to the SLPP documentation: https://en.opensuse.org/openSUSE:Shared_library_packaging_policy#Package_na… -- You are receiving this mail because: You are on the CC list for the bug.

1 12

[Bug 1182880] New: Window decoration does not appear correctly
by bugzilla_noreply＠suse.com 26 May '22

26 May '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1182880 Bug ID: 1182880 Summary: Window decoration does not appear correctly Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: antoine(a)copernic.xyz QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 846634 --> http://bugzilla.opensuse.org/attachment.cgi?id=846634&action=edit window decoration Window decoration does not appear correctly on opensuse tumbleweed xfce. (see picture attached) michel@ninja:~> sudo lspci -nnk | grep -A3 VGA [sudo] Mot de passe de root�: 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation G98 [GeForce 9300 GE] [10de:06e0] (rev a1) Subsystem: LeadTek Research Inc. Device [107d:5aa7] Kernel driver in use: nouveau Kernel modules: nouveau michel@ninja:~> uname -a Linux ninja 5.10.16-1-default #1 SMP Sat Feb 13 16:20:19 UTC 2021 (11381f3) x86_64 x86_64 x86_64 GNU/Linux michel@ninja:~> lsb_release -a LSB Version: n/a Distributor ID: openSUSE Description: openSUSE Tumbleweed Release: 20210223 Codename: n/a michel@ninja:~> I tried few ways to solve this issue 1 > I run "xfwm4 --replace" and it works (but I have to do this at every reboot) 2 > Turning off auto-login solves this issue (I do not understand why) 3 > I tried to install nvidia drivers but they do not exist for my hardware on tumbleweed -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1190960] New: pam_ssh: use %_pam_moduledir
by bugzilla_noreply＠suse.com 26 May '22

26 May '22

https://bugzilla.suse.com/show_bug.cgi?id=1190960 Bug ID: 1190960 Summary: pam_ssh: use %_pam_moduledir Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: pmonrealgonzalez(a)suse.com Reporter: lnussel(a)suse.com QA Contact: qa-bugs(a)suse.de Blocks: 1190946 Found By: --- Blocker: --- The pam package offers a number of macros to avoid hardcoding directory names in spec files: https://build.opensuse.org/package/view_file/openSUSE:Factory/pam/macros.pam Please consider using at least the %_pam_moduledir macro in order to have the package follow UsrMerge. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1156920] New: latest wpa_supplicant seems broken (2.9-1.1)
by bugzilla_noreply＠novell.com 26 May '22

26 May '22

http://bugzilla.suse.com/show_bug.cgi?id=1156920 Bug ID: 1156920 Summary: latest wpa_supplicant seems broken (2.9-1.1) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: roger.whittaker(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Unable to connect to wireless with wpa_supplicant-2.9-1.1.x86_64. Downgrade to wpa_supplicant-2.6-9.1.x86_64.rpm solved the problem. With 2.9-1.1, in /var/log/wpa_supplicant.log 1573837618.431976: wlp59s0: SME: Trying to authenticate with e4:95:6e:40:df:9d (SSID='rogeroffice' freq=2462 MHz) 1573837618.512991: wlp59s0: CTRL-EVENT-AUTH-REJECT e4:95:6e:40:df:9d auth_type=0 auth_transaction=2 status_code=1 1573837619.360496: wlp59s0: SME: Trying to authenticate with e4:95:6e:40:df:9d (SSID='rogeroffice' freq=2462 MHz) 1573837619.431234: wlp59s0: CTRL-EVENT-AUTH-REJECT e4:95:6e:40:df:9d auth_type=0 auth_transaction=2 status_code=1 1573837622.973427: wlp59s0: SME: Trying to authenticate with e4:95:6e:40:df:9d (SSID='rogeroffice' freq=2462 MHz) 1573837623.047145: wlp59s0: CTRL-EVENT-AUTH-REJECT e4:95:6e:40:df:9d auth_type=0 auth_transaction=2 status_code=1 1573837624.903588: wlp59s0: SME: Trying to authenticate with e4:95:6e:40:df:9d (SSID='rogeroffice' freq=2462 MHz) 1573837624.987293: wlp59s0: CTRL-EVENT-AUTH-REJECT e4:95:6e:40:df:9d auth_type=0 auth_transaction=2 status_code=1 1573837624.987338: wlp59s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="rogeroffice" auth_failures=1 duration=10 reason=CONN_FAILED 1573837634.854847: wlp59s0: CTRL-EVENT-SSID-REENABLED id=0 ssid="rogeroffice" 1573837634.854985: wlp59s0: SME: Trying to authenticate with e4:95:6e:40:df:9d (SSID='rogeroffice' freq=2462 MHz) 1573837634.935453: wlp59s0: CTRL-EVENT-AUTH-REJECT e4:95:6e:40:df:9d auth_type=0 auth_transaction=2 status_code=1 1573837634.935488: wlp59s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="rogeroffice" auth_failures=2 duration=20 reason=CONN_FAILED 1573837636.533619: wlp59s0: Reject scan trigger since one is already pending 1573837729.947335: nl80211: deinit ifname=p2p-dev-wlp59s0 disabled_11b_rates=0 1573837730.103068: nl80211: deinit ifname=wlp59s0 disabled_11b_rates=0 After downgrade: 1573839996.915081: wlp59s0: Trying to associate with e4:95:6e:40:df:9d (SSID='rogeroffice' freq=2462 MHz) 1573839996.973165: wlp59s0: Associated with e4:95:6e:40:df:9d 1573839996.990751: wlp59s0: WPA: Key negotiation completed with e4:95:6e:40:df:9d [PTK=CCMP GTK=CCMP] 1573839996.990876: wlp59s0: CTRL-EVENT-CONNECTED - Connection to e4:95:6e:40:df:9d completed [id=0 id_str=] -- You are receiving this mail because: You are on the CC list for the bug.

2 23

[Bug 1182549] New: RTW: Error, streaming errors stops wifi network.
by bugzilla_noreply＠suse.com 26 May '22

26 May '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1182549 Bug ID: 1182549 Summary: RTW: Error, streaming errors stops wifi network. Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: graeme.w.murray(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:85.0) Gecko/20100101 Firefox/85.0 Build Identifier: RTW: ERROR [RFK-CHK] RF-K not allowed due to ifaces under site-survey The above message streams into the journal and while this is happening the wifi network stops with dropped packets and ping delays of more than 6 secs to the router. Setting BSSID on the network does not fix this. Reproducible: Always Steps to Reproduce: 1.connect to the network using network manager 2. 3. Actual Results: Streaming errors Expected Results: No errors -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1191769] New: [SLPP] libvisual: E: shlib-policy-name-error
by bugzilla_noreply＠suse.com 26 May '22

26 May '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1191769 Bug ID: 1191769 Summary: [SLPP] libvisual: E: shlib-policy-name-error Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: martin.liska(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The following rpmlint error was seen for the package: libvisual.log:[ 69s] libvisual.x86_64: E: shlib-policy-name-error SONAME: libvisual-0.4.so.0, expected package suffix: 0_4-0 Note the updated rpmlint will reach openSUSE:Factory soon. We would like to make 'shlib-policy-name-error' a package build failure error, so please fix the error. Link to the SLPP documentation: https://en.opensuse.org/openSUSE:Shared_library_packaging_policy#Package_na… -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1191776] New: [SLPP] pacemaker: E: shlib-policy-name-error
by bugzilla_noreply＠suse.com 26 May '22

26 May '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1191776 Bug ID: 1191776 Summary: [SLPP] pacemaker: E: shlib-policy-name-error Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: martin.liska(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The following rpmlint error was seen for the package: pacemaker.log:[ 334s] libpacemaker3.x86_64: E: shlib-policy-name-error SONAME: libcib.so.27, expected package suffix: 27 pacemaker.log:[ 334s] libpacemaker3.x86_64: E: shlib-policy-name-error SONAME: libcrmcluster.so.29, expected package suffix: 29 pacemaker.log:[ 334s] libpacemaker3.x86_64: E: shlib-policy-name-error SONAME: libcrmcommon.so.34, expected package suffix: 34 pacemaker.log:[ 334s] libpacemaker3.x86_64: E: shlib-policy-name-error SONAME: libcrmservice.so.28, expected package suffix: 28 pacemaker.log:[ 334s] libpacemaker3.x86_64: E: shlib-policy-name-error SONAME: liblrmd.so.28, expected package suffix: 28 pacemaker.log:[ 334s] libpacemaker3.x86_64: E: shlib-policy-name-error SONAME: libpacemaker.so.1, expected package suffix: 1 pacemaker.log:[ 334s] libpacemaker3.x86_64: E: shlib-policy-name-error SONAME: libpe_rules.so.26, expected package suffix: 26 pacemaker.log:[ 334s] libpacemaker3.x86_64: E: shlib-policy-name-error SONAME: libpe_status.so.28, expected package suffix: 28 pacemaker.log:[ 334s] libpacemaker3.x86_64: E: shlib-policy-name-error SONAME: libstonithd.so.26, expected package suffix: 26 Note the updated rpmlint will reach openSUSE:Factory soon. We would like to make 'shlib-policy-name-error' a package build failure error, so please fix the error. Link to the SLPP documentation: https://en.opensuse.org/openSUSE:Shared_library_packaging_policy#Package_na… -- You are receiving this mail because: You are on the CC list for the bug.

1 5