August 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1228808] New: grub error: ../../grub-core/script/function.c:119:can't find command `None'. error: ../../grub-core/commands/terminal.c:113:terminal `serial' isn't found. error: ../../grub-core/commands/terminal.c:113:terminal `serial' isn't found.
by bugzilla_noreply＠suse.com 02 Aug '24

02 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1228808 Bug ID: 1228808 Summary: grub error: ../../grub-core/script/function.c:119:can't find command `None'. error: ../../grub-core/commands/terminal.c:113:terminal `serial' isn't found. error: ../../grub-core/commands/terminal.c:113:terminal `serial' isn't found. Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: vinaygahlout(a)google.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Hello, currently instance built with openSUSE-15.5 and 15.6 images provided on GCP have below errors in Serial console logs: [0m[37m[40merror: ../../grub-core/script/function.c:119:can't find command `None'. error: ../../grub-core/commands/terminal.c:113:terminal `serial' isn't found. error: ../../grub-core/commands/terminal.c:113:terminal `serial' isn't found. [0m[30m[40m[2J[01;01H[0m[37m[40m[02;30HGNU GRUB version 2.06 Although instance is able to boot without any issue, but a customer reached out asking why its happening. Is this expected behaviour for openSuse-leap-15.5 instance ? ================================================= Kernel version: 5.14.21-150500.55.62-default opensuse-leap-15-5:~ # cat /etc/os-release NAME="openSUSE Leap" VERSION="15.5" ID="opensuse-leap" ID_LIKE="suse opensuse" VERSION_ID="15.5" PRETTY_NAME="openSUSE Leap 15.5" ANSI_COLOR="0;32" CPE_NAME="cpe:/o:opensuse:leap:15.5" BUG_REPORT_URL="https://bugs.opensuse.org" HOME_URL="https://www.opensuse.org/" DOCUMENTATION_URL="https://en.opensuse.org/Portal:Leap" LOGO="distributor-logo-Leap" opensuse-leap-15-5:~ # opensuse-leap-15-5:~ # cat /etc/default/grub # If you change this file, run 'grub2-mkconfig -o /boot/grub2/grub.cfg' afterwards to update # /boot/grub2/grub.cfg. # Uncomment to set your own custom distributor. If you leave it unset or empty, the default # policy is to determine the value from /etc/os-release # GRUB_DISTRIBUTOR="" GRUB_DEFAULT=0 GRUB_HIDDEN_TIMEOUT=0 GRUB_HIDDEN_TIMEOUT_QUIET=true GRUB_TIMEOUT=1 GRUB_CMDLINE_LINUX_DEFAULT="console=ttyS0,38400n8 net.ifnames=0 dis_ucode_ldr multipath=off" GRUB_CMDLINE_LINUX="root=LABEL=ROOT" # Uncomment to automatically save last booted menu entry in GRUB2 environment # variable `saved_entry' #GRUB_SAVEDEFAULT="true" # Uncomment to enable BadRAM filtering, modify to suit your needs # This works with Linux (no patch required) and with any kernel that obtains # the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...) #GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef" # Uncomment to disable graphical terminal (grub-pc only) #GRUB_TERMINAL=console # The resolution used on graphical terminal # note that you can use only modes which your graphic card supports via VBE # you can see them in real GRUB with the command `vbeinfo' #GRUB_GFXMODE=640x480 # Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux #GRUB_DISABLE_LINUX_UUID=true # Uncomment to disable generation of recovery mode menu entries #GRUB_DISABLE_RECOVERY="true" # Uncomment to get a beep at grub start #GRUB_INIT_TUNE="480 440 1" GRUB_DISABLE_LINUX_UUID=true GRUB_DISTRIBUTOR="openSUSE-Leap-15.5" GRUB_ENABLE_LINUX_LABEL=true GRUB_GFXMODE=auto #GRUB_SERIAL_COMMAND="None" GRUB_TERMINAL_INPUT="console" GRUB_TERMINAL_OUTPUT="console" SUSE_REMOVE_LINUX_ROOT_PARAM=true ================================================= I tested with one of the instance, and this can be fixed by changing options in /etc/default/grub from GRUB_SERIAL_COMMAND="None" GRUB_TERMINAL_INPUT="serial" GRUB_TERMINAL_OUTPUT="serial" to #GRUB_SERIAL_COMMAND="None" GRUB_TERMINAL_INPUT="console" GRUB_TERMINAL_OUTPUT="console" Can someone please confirm if this is a bug and if we can permanently fix this in image. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1198722] initialize useful compiled in LSMs by default
by bugzilla_noreply＠suse.com 02 Aug '24

02 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1198722 https://bugzilla.suse.com/show_bug.cgi?id=1198722#c9 OpenSUSE Account <opensuse.k1akb(a)slmail.me> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |opensuse.k1akb(a)slmail.me --- Comment #9 from OpenSUSE Account <opensuse.k1akb(a)slmail.me> --- I discovered that 'yama' is not enabled in Leap 15.6. I'm similarly wondering if there are reasons to leave those out. As this report proves, there is awareness of these missing/left-out mechanisms. (I won't make a new report for Leap 15.6, as this exists already.) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1228770] After upgrade from shadow 4.8.1-150600.15.45 → 4.8.1-150600.17.3.1, not all contents of /etc/skel get added to the newusers home directory
by bugzilla_noreply＠suse.com 02 Aug '24

02 Aug '24

https://bugzilla.suse.com/show_bug.cgi?id=1228770 https://bugzilla.suse.com/show_bug.cgi?id=1228770#c2 Michael Vetter <mvetter(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |IN_PROGRESS --- Comment #2 from Michael Vetter <mvetter(a)suse.com> --- Found the issue and prepared some patches. After some more testing and applying to all codestreams I will create a new submission. Mistake was in above mentioned patch. -- 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#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