July 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1228425] Trace in sysfs during setup of hvc
by bugzilla_noreply＠suse.com 30 Jul '24

30 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1228425 Sarah Kriesch <ada.lovelace(a)gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tstaudt(a)de.ibm.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1228425] Trace in sysfs during setup of hvc
by bugzilla_noreply＠suse.com 30 Jul '24

30 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1228425 https://bugzilla.suse.com/show_bug.cgi?id=1228425#c5 --- Comment #5 from Sarah Kriesch <ada.lovelace(a)gmx.de> --- Used kernel-source version: 6.10.2-1.1 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1228425] Trace in sysfs during setup of hvc
by bugzilla_noreply＠suse.com 30 Jul '24

30 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1228425 https://bugzilla.suse.com/show_bug.cgi?id=1228425#c4 --- Comment #4 from Sarah Kriesch <ada.lovelace(a)gmx.de> --- Hello Marcus, Can you mirror this bug report to IBM and forward that to the Kernel Developers, please? We can not install openSUSE Tumbleweed with the latest kernel at the moment. Here are our openQA results: https://openqa.opensuse.org/tests/4367326#step/bootloader_s390/35 In the best case, you will forward this bug to Heiko Carstens and Alexander Gordeev, because the referenced commits affecting this situation are from them. (In reply to Miroslav Franc from comment #3) > Reverting > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/ > ?id=effb83572685eaa70d05a8dd6307ca574a11fcf3 > and > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/ > ?id=ccec5032291b108e694b55394cd035c9d840052a > makes it disappear. > > I'm not yet sure what's the problem. Those patches should not change the > kernel's behavior. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1228425] Trace in sysfs during setup of hvc
by bugzilla_noreply＠suse.com 30 Jul '24

30 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1228425 Sarah Kriesch <ada.lovelace(a)gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |marcus.kraft1(a)ibm.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1226157] sssd: missing /etc/sssd/sssd.conf
by bugzilla_noreply＠suse.com 30 Jul '24

30 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1226157 https://bugzilla.suse.com/show_bug.cgi?id=1226157#c11 Samuel Cabrero <scabrero(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |FIXED --- Comment #11 from Samuel Cabrero <scabrero(a)suse.com> --- The config file part is released and the sssd-32bit package will be added to the repositories soon. Thank you for your comments, please reopen if necessary. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1228438] [Build 20240729] openQA test fails in enable_systemd: WSL2 vs systemd 256
by bugzilla_noreply＠suse.com 30 Jul '24

30 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1228438 https://bugzilla.suse.com/show_bug.cgi?id=1228438#c5 --- Comment #5 from Franck Bui <fbui(a)suse.com> --- (In reply to Fabian Vogt from comment #4) > Maybe it's possible to somehow work around this downstream by ignoring the > inherited cgroup hierarchy and just setting up a v2 one? I'm not sure to see what you mean by setting up a cgroupv2 hierarchy downstream. The environment of the container is usually set up by the container manager (WSL in this case), systemd inside the container just reacts accordingly. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1228438] [Build 20240729] openQA test fails in enable_systemd: WSL2 vs systemd 256
by bugzilla_noreply＠suse.com 30 Jul '24

30 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1228438 https://bugzilla.suse.com/show_bug.cgi?id=1228438#c4 --- Comment #4 from Fabian Vogt <fvogt(a)suse.com> --- (In reply to Franck Bui from comment #3) > Just providing some updates based on my understanding of the test after > Fabian did some investigation (thanks a lot Fabian). > > Apparently `wsl /bin/bash -c "systemctl is-systemd-running` creates an > environment (container) based on the host environment before executing bash > in the container. > > More specifically, the hybrid cgroup hierarchy of the host is reused by the > container. However since commit f2512de82dc91cfb742a4f4df934bdb4fcad482d, > systemd makes systems based on the legacy cgroup harder to boot by incurring > a delay of 30 sec to the boot process. I filed a new report at WSL: https://github.com/microsoft/WSL/issues/11857 Maybe it's possible to somehow work around this downstream by ignoring the inherited cgroup hierarchy and just setting up a v2 one? > This probably explains why the command `wsl /bin/bash -c "systemctl > is-systemd-running` is failing to contact PID1 in the container. Sleeping > for 30 sec before executing the command should work around the issue. > > That said it's not clear to me how this is supposed to work reliably even > with v255, ie how `wsl` figures out when it's safe to contact PID1. I have no idea. That's completely in opaque, proprietary and undocumented code. > PS: Fabian, please correct me if anything I wrote is incorrect. All correct. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1228438] [Build 20240729] openQA test fails in enable_systemd: WSL2 vs systemd 256
by bugzilla_noreply＠suse.com 30 Jul '24

30 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1228438 Franck Bui <fbui(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fvogt(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1228438] [Build 20240729] openQA test fails in enable_systemd: WSL2 vs systemd 256
by bugzilla_noreply＠suse.com 30 Jul '24

30 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1228438 https://bugzilla.suse.com/show_bug.cgi?id=1228438#c3 --- Comment #3 from Franck Bui <fbui(a)suse.com> --- Just providing some updates based on my understanding of the test after Fabian did some investigation (thanks a lot Fabian). Apparently `wsl /bin/bash -c "systemctl is-systemd-running` creates an environment (container) based on the host environment before executing bash in the container. More specifically, the hybrid cgroup hierarchy of the host is reused by the container. However since commit f2512de82dc91cfb742a4f4df934bdb4fcad482d, systemd makes systems based on the legacy cgroup harder to boot by incurring a delay of 30 sec to the boot process. This probably explains why the command `wsl /bin/bash -c "systemctl is-systemd-running` is failing to contact PID1 in the container. Sleeping for 30 sec before executing the command should work around the issue. That said it's not clear to me how this is supposed to work reliably even with v255, ie how `wsl` figures out when it's safe to contact PID1. PS: Fabian, please correct me if anything I wrote is incorrect. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1228420] libzypp 17.35.4 breaks yast2-* build
by bugzilla_noreply＠suse.com 30 Jul '24

30 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1228420 https://bugzilla.suse.com/show_bug.cgi?id=1228420#c9 --- Comment #9 from Michael Andres <ma(a)suse.com> --- Fixed in libzypp-17.35.6: A few more symbols for 15.3 YAST versions. -- You are receiving this mail because: You are on the CC list for the bug.

1 0