August 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1228621] [Build 9.32] openSUSE agama live installer iso failed to boot for dracut report error and entered emergency mode
by bugzilla_noreply＠suse.com 02 Aug '24

02 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1228621 https://bugzilla.suse.com/show_bug.cgi?id=1228621#c14 --- Comment #14 from Thomas Blume <thomas.blume(a)suse.com> --- (In reply to Antonio Feijoo from comment #13) > (In reply to Thomas Blume from comment #12) > > > https://github.com/openSUSE/dracut/blob/SUSE/059/modules.d/90livenet/ > > > livenetroot.sh > > > > shows that the size check for live images inclusive error handling is > > already implemented. > > Obviously the injection is redundant therewith. > > In that case the images.sh script can just be deleted from the kiwi build. > > But the implemented error handling expects `rd.writable.fsimg`. I don't know > it this kernel command line option is used with agama... at least this > openQA test does not include it. Yeah, this is because only in the rw case the whole image is copied into RAM, and hence has additional memory requirements. If the image is ro, it is used directly and hence doesn't need additional RAM. I've checked the age of images.sh in my private agama project and it is March 4th 2023. So, this is older than the commit to the dracut git: https://github.com/dracutdevs/dracut/commit/52351cfa049a9594d539e6a5337d591… AFAICR, I've used that injection of the memory check via images.sh during my testphase for this commit. Not sure how it went into the official agama sources but it should be obsolete now. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1228621] [Build 9.32] openSUSE agama live installer iso failed to boot for dracut report error and entered emergency mode
by bugzilla_noreply＠suse.com 02 Aug '24

02 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1228621 https://bugzilla.suse.com/show_bug.cgi?id=1228621#c13 --- Comment #13 from Antonio Feijoo <antonio.feijoo(a)suse.com> --- (In reply to Thomas Blume from comment #12) > > https://github.com/openSUSE/dracut/blob/SUSE/059/modules.d/90livenet/ > > livenetroot.sh > > shows that the size check for live images inclusive error handling is > already implemented. > Obviously the injection is redundant therewith. > In that case the images.sh script can just be deleted from the kiwi build. But the implemented error handling expects `rd.writable.fsimg`. I don't know it this kernel command line option is used with agama... at least this openQA test does not include it. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1228797] python3-schema and python3-daemon not available with sle-module-pythons
by bugzilla_noreply＠suse.com 02 Aug '24

02 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1228797 https://bugzilla.suse.com/show_bug.cgi?id=1228797#c1 --- Comment #1 from OBSbugzilla Bot <bwiedemann+obsbugzillabot(a)suse.com> --- This is an autogenerated message for OBS integration: This bug (1228797) was mentioned in https://build.opensuse.org/request/show/1191194 Backports:SLE-15-SP6 / python-schema -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1228805] New: Uninstall orphaned "openSUSE-release-dvd" will uninstall whole system
by bugzilla_noreply＠suse.com 02 Aug '24

02 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1228805 Bug ID: 1228805 Summary: Uninstall orphaned "openSUSE-release-dvd" will uninstall whole system Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: dev.dorrejo(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Hello, Today trying to clean my OS with the next script: zypper rm -u $(zypper pa --unneeded --orphaned | cut -d '|' -f 3 | awk 'NR>4') Will end with uninstalling practically the whole system, this behavior in my opinion is not the correct one. This behavior change if openSUSE-release-ftp is installed before doing this. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1228804] New: Regression: qemu-uefi-aarch64 does not work with virtualization=on anymore
by bugzilla_noreply＠suse.com 02 Aug '24

02 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1228804 Bug ID: 1228804 Summary: Regression: qemu-uefi-aarch64 does not work with virtualization=on anymore Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Virtualization:Other Assignee: jlee(a)suse.com Reporter: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de CC: virt-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- qemu-system-aarch64 -M virt,virtualization=on -cpu max -m 4G -smp 4 -bios /usr/share/qemu/aavmf-aarch64-code.bin -serial stdio used to work with qemu-uefi-aarch64-202208-150500.4.1.noarch (From 15.5) but does not work with newer versions such as qemu-uefi-aarch64-202402-1.1.noarch (from TW), it just data aborts immediately before any output (visible with -d int). The latest build from linaro works fine though: wget https://snapshots.linaro.org/components/kernel/leg-virt-tianocore-edk2-upst… qemu-system-aarch64 -M virt,virtualization=on -cpu max -m 4G -smp 4 -bios QEMU_EFI.fd -serial stdio -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1228621] [Build 9.32] openSUSE agama live installer iso failed to boot for dracut report error and entered emergency mode
by bugzilla_noreply＠suse.com 02 Aug '24

02 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1228621 https://bugzilla.suse.com/show_bug.cgi?id=1228621#c12 --- Comment #12 from Thomas Blume <thomas.blume(a)suse.com> --- (In reply to Thomas Blume from comment #11) > Hm, that was indeed my approach for injecting a memory size check for > livenetroot for the agama initrd that is build with kiwi. > But, I don't remember that I submitted that anywhere. > > However, it's missing error handling for the case that curl cannot retrieve > the Content-Length setting. > I will work on it. Argh, I should read more carefully: > https://github.com/openSUSE/dracut/blob/SUSE/059/modules.d/90livenet/ > livenetroot.sh shows that the size check for live images inclusive error handling is already implemented. Obviously the injection is redundant therewith. In that case the images.sh script can just be deleted from the kiwi build. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1206950] (podman) dnsname plugin isn't available so containers can't resolve each other
by bugzilla_noreply＠suse.com 02 Aug '24

02 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1206950 https://bugzilla.suse.com/show_bug.cgi?id=1206950#c4 Alexandre Vicenzi <alexandre.vicenzi(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|containers-bugowner(a)suse.de |alexandre.vicenzi(a)suse.com Status|NEW |RESOLVED Resolution|--- |INVALID CC| |alexandre.vicenzi(a)suse.com, | |containers-bugowner(a)suse.de --- Comment #4 from Alexandre Vicenzi <alexandre.vicenzi(a)suse.com> --- I'm not able to reproduce this using a compose file that has `depends_on` and `links` to another container. cni-plugin-dnsname is not installed on my machine. From the official README [1]. podman dnsname plugin: It is usually found in the podman-plugins or podman-dnsname distro packages, those packages are not pulled by default and you need to install them. This allows containers to be able to resolve each other if they are on the same CNI network. This is not necessary when podman is using netavark as a network backend. Tumbleweed uses netavark, you can see it with `podman info`: networkBackendInfo: backend: netavark This is not an issue, if netavark is not used, you need to manually install an additional package. Something to consider, as of 2023, the dnsname plugin is no longer actively maintained, it reached EOL. [1]: https://github.com/containers/podman-compose?tab=readme-ov-file#podman-comp… -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1224773] NVIDIA KMP: initrd not regenerated on transactional systems using systemd-boot like Aeon >= RC2
by bugzilla_noreply＠suse.com 02 Aug '24

02 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1224773 https://bugzilla.suse.com/show_bug.cgi?id=1224773#c54 Stefan Dirsch <sndirsch(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(sunscape1@hotmail |needinfo?(vortex(a)z-ray.de) |.com) | --- Comment #54 from Stefan Dirsch <sndirsch(a)suse.com> --- (correcting NEEDINFO) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1204318] podman unable to delete infrastructure infra container, TW 20221012
by bugzilla_noreply＠suse.com 02 Aug '24

02 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1204318 https://bugzilla.suse.com/show_bug.cgi?id=1204318#c1 Alexandre Vicenzi <alexandre.vicenzi(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |INVALID CC| |alexandre.vicenzi(a)suse.com, | |containers-bugowner(a)suse.de Assignee|containers-bugowner(a)suse.de |alexandre.vicenzi(a)suse.com Status|NEW |RESOLVED --- Comment #1 from Alexandre Vicenzi <alexandre.vicenzi(a)suse.com> --- I was not able to reproduce the same error in Tumbleweed. If you have running or paused containers they cannot be removed without force. In this case, the proper way to remove is to stop the containers first. podman pod stop db podman pod rm db -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1227908] auditd obsolete built-in options
by bugzilla_noreply＠suse.com 02 Aug '24

02 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1227908 https://bugzilla.suse.com/show_bug.cgi?id=1227908#c8 Fabian Vogt <fvogt(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo? | CC| |fvogt(a)suse.com --- Comment #8 from Fabian Vogt <fvogt(a)suse.com> --- FWICT this was introduced by https://github.com/linux-audit/audit-userspace/commit/d1ccd8f642e11ad65cdc8…, which added a log entry with "auid=42". This is something for upstream to figure out how to fix IMO. I see several options: a) Remove the gdm part again b) Use some uid that doesn't exist and hardcode unknown(123456) c) Start auparse in a test mode that ignores the host system and maps 42 to gdm. Downstream this could be hacked around using a patch that does s/gdm/unknown(42)/. That would work in OBS, but if someone builds that locally (sholudn't be that common) it would fail in the case that 42 is assigned to something. -- You are receiving this mail because: You are on the CC list for the bug.

1 0