September 2022 - openSUSE Kubic Bugs - openSUSE Mailing Lists

[Bug 1203393] New: microOS cloud-init (OpenStack variant) fails due to attempting systemd-network over NetworkManager
by bugzilla_noreply＠suse.com 21 Apr '23

21 Apr '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1203393 Bug ID: 1203393 Summary: microOS cloud-init (OpenStack variant) fails due to attempting systemd-network over NetworkManager Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: MicroOS Assignee: kubic-bugs(a)opensuse.org Reporter: matt(a)traverse.com.au QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:104.0) Gecko/20100101 Firefox/104.0 Build Identifier: When using an OpenStack-ContainerHost [aarch64] microOS Tumbleweed build (from https://en.opensuse.org/Portal:MicroOS) cloud-init will fail as it tries to create a file with a systemd-network UID. Despite NetworkManager being the microOS 'default', and systemd-network not being installed, cloud-init decides to create for systemd-networkd You do not even need to have a valid cloud-init source for this, the issue will occur on a 'fresh' system, verified by examining the log files after first boot ---------------------------------------------- 2022-09-14 06:54:40,414 - util.py[DEBUG]: Writing to /etc/systemd/network/10-cloud-init-eth0.network - wb: [644] 69 bytes 2022-09-14 06:54:40,416 - util.py[WARNING]: failed stage init-local 2022-09-14 06:54:40,417 - util.py[DEBUG]: failed stage init-local Traceback (most recent call last): File "/usr/lib/python3.10/site-packages/cloudinit/util.py", line 1430, in chownbyname uid = pwd.getpwnam(user).pw_uid KeyError: "getpwnam(): name not found: 'systemd-network'" The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/usr/lib/python3.10/site-packages/cloudinit/cmd/main.py", line 689, in status_wrapper ret = functor(name, args) File "/usr/lib/python3.10/site-packages/cloudinit/cmd/main.py", line 398, in main_init init.apply_network_config(bring_up=bring_up_interfaces) [edited for brevity, I will attach the full log separately] OSError: Unknown user or group: "getpwnam(): name not found: 'systemd-network'" ---------------------------------------------- I built a custom microOS image (see https://build.opensuse.org/package/revisions/home:mcbridematt:branches:deve… ) with systemd-network installed and verified this "resolves" the issue. However, I haven't tried to diagnose why cloud-init wants to use networkd over NetworkManager. Reproducible: Always Steps to Reproduce: 1. Boot a microOS Tumbleweed VM with a cloud-init file (e.g cidata image) 2. Attempt to use system once it reaches the login prompt (for example, using credentials or SSH keys set in the supplied cloud-config) Actual Results: Login fails because cloud-init did not complete. No mention of the cloud-init failure is provided to the user at the console (except maybe the hostname not being configured by cloud-init) , it can only be discovered by examining the /var partition offline. The specific image I am using is: openSUSE-MicroOS.aarch64-16.0.0-OpenStack-Cloud-Snapshot20220911.qcow2 -- You are receiving this mail because: You are the assignee for the bug.

1 8

[Bug 1200457] New: iscsi.service cannot start at microos
by bugzilla_noreply＠suse.com 10 Jan '23

10 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1200457 Bug ID: 1200457 Summary: iscsi.service cannot start at microos Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: MicroOS Assignee: kubic-bugs(a)opensuse.org Reporter: matwey.kornilov(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hello, I am running microOS 20220611 with open-iscsi-2.1.7-90.1.x86_64. When I try to start iscsi.service the following error appears: Jun 12 19:16:09 localhost.localdomain systemd[1]: Starting Login and scanning of iSCSI devices... Jun 12 19:16:09 localhost.localdomain iscsiadm[1009]: iscsiadm: Maybe you are not root? Jun 12 19:16:09 localhost.localdomain iscsiadm[1009]: iscsiadm: Could not lock discovery DB: /etc/iscsi/lock.write: No such file or directory Jun 12 19:16:09 localhost.localdomain iscsiadm[1009]: iscsiadm: No records found Jun 12 19:16:09 localhost.localdomain iscsiadm[1017]: iscsiadm: Maybe you are not root? Jun 12 19:16:09 localhost.localdomain iscsiadm[1017]: iscsiadm: Could not lock discovery DB: /etc/iscsi/lock.write: No such file or directory Jun 12 19:16:09 localhost.localdomain iscsiadm[1017]: iscsiadm: No records found Jun 12 19:16:09 localhost.localdomain iscsiadm[1018]: iscsiadm: Could not get list of targets from firmware. (err 21) Jun 12 19:16:09 localhost.localdomain systemd[1]: Finished Login and scanning of iSCSI devices. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[kubic-bugs] [Bug 1167780] New: MicroOS images don't update grub if booted without EFI
by bugzilla_noreply＠novell.com 09 Jan '23

09 Jan '23

http://bugzilla.suse.com/show_bug.cgi?id=1167780 Bug ID: 1167780 Summary: MicroOS images don't update grub if booted without EFI Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: MicroOS Assignee: fvogt(a)suse.com Reporter: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de CC: kubic-bugs(a)opensuse.org Found By: --- Blocker: --- The .qcow2 images are meant to work fine on systems with EFI (optionally secure boot) and without, so they have both i386-pc and x86_64-efi targets of grub2 installed by kiwi during image building. Kiwi sets LOADER_TYPE="grub2-efi" for this. When booting the image without EFI though, this is not changed by anything and so update-bootloader only manages the x86_64-efi target of grub2. As the grub.cfg file is in the same location, there aren't any immediate issues, but it means that grub is never updated in those deployments. -- You are receiving this mail because: You are on the CC list for the bug.

2 13

[Bug 1203425] New: gvfs-backend-samba not installed, needed for SMB support in gnome files
by bugzilla_noreply＠suse.com 23 Dec '22

23 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1203425 Bug ID: 1203425 Summary: gvfs-backend-samba not installed, needed for SMB support in gnome files Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: MicroOS Assignee: kubic-bugs(a)opensuse.org Reporter: pranav.sharma.ama(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- without the package installed, gnome files will fail with an error saying it can't mount an smb share, forcing the user to install with t-u. -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1202875] New: MicroOS Desktop: Can't start packagekitd due libdnf/libtukit symbol error
by bugzilla_noreply＠suse.com 23 Dec '22

23 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1202875 Bug ID: 1202875 Summary: MicroOS Desktop: Can't start packagekitd due libdnf/libtukit symbol error Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: MicroOS Assignee: kubic-bugs(a)opensuse.org Reporter: michal.vyskocil(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- packagekitd won't start on my MicroOS GNOME Desktop and produces error messages in Gnome Software. NAME="openSUSE Tumbleweed" # VERSION="20220827" packagekitd[28073]: what(): Can't load plugin "txnupd.so": Can't load shared library "/usr/lib64/libdnf/plugins/txnupd.so": /usr/lib64/libdnf/plugins/txnupd.so: undefined symbol: _ZN19TransactionalUpdate11Transaction4initENSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE It looks like this commit https://github.com/openSUSE/transactional-update/commit/2a2117d15a87dfbedea… broke the ABI. Not sure why BuildService haven't solved the problem by rebuilding the package. What libtukit.so.4 provides (I run my setup inside distrobox, hence /run/host paths poiting to the "host" - the MicroOS itself) objdump -C -T /run/host/lib64/libtukit.so.4.0.0 | grep 'Transaction::init' 0000000000020010 g DF .text 0000000000000c7f Base TransactionalUpdate::Transaction::init(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::optional<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > >) What txnupd requires objdump -C -T /run/host/lib64/libdnf/plugins/txnupd.so | grep 'Transaction::init' 0000000000000000 DF *UND* 0000000000000000 Base TransactionalUpdate::Transaction::init(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >) $ rpm -qf /lib64/libdnf/plugins/txnupd.so /lib64/libtukit.so.4.0.0 libdnf-plugin-txnupd-0.1.3-1.10.x86_64 libtukit4-4.0.1-1.1.x86_64 -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 1202290] New: Unable to update system using GNOME Software
by bugzilla_noreply＠suse.com 23 Dec '22

23 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1202290 Bug ID: 1202290 Summary: Unable to update system using GNOME Software Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: MicroOS Assignee: kubic-bugs(a)opensuse.org Reporter: songchuan.kang(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:103.0) Gecko/20100101 Firefox/103.0 Build Identifier: In GNOME Software, when clicking "Restart & Update" button in updates tab, an error messages pops up saying: > Unable to update "System Updates": Failed to create symlink: Read-only file system This is due to GNOME Software trying to call pk-trigger-offline-update which creates /system-update. However, this won't succeed because of the read-only file system. Reproducible: Always -- You are receiving this mail because: You are the assignee for the bug.

1 5

[Bug 1201566] New: setroubleshoot packages in repositories bundle a broken version of setroubleshootd
by bugzilla_noreply＠suse.com 23 Dec '22

23 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1201566 Bug ID: 1201566 Summary: setroubleshoot packages in repositories bundle a broken version of setroubleshootd Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: openSUSE Tumbleweed Status: NEW Severity: Minor Priority: P5 - None Component: MicroOS Assignee: kubic-bugs(a)opensuse.org Reporter: systemtool.exe(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The setroubleshoot-server 3.3.26 package bundles a version of setroubleshootd that requires a python2 module but is executed with python3 (as the shebang in the executable is /usr/bin/python3). The issue has been resolved in later versions. -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1203887] New: Cannot changr auto-login settings (Gnome Settings)
by bugzilla_noreply＠suse.com 22 Dec '22

22 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1203887 Bug ID: 1203887 Summary: Cannot changr auto-login settings (Gnome Settings) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: MicroOS Assignee: kubic-bugs(a)opensuse.org Reporter: cutelilfroggy(a)protonmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Trying to change the auto-login settings under Gnome Settings -> Users fails. You can push the little slider to turn auto-login on, but that setting change is not respected. If you switch to a different category in the setting menu or restart the setting app, the slider is also back to its previous state. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1203427] New: distrobox should be installed by default for microos desktop
by bugzilla_noreply＠suse.com 22 Dec '22

22 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1203427 Bug ID: 1203427 Summary: distrobox should be installed by default for microos desktop Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Enhancement Priority: P5 - None Component: MicroOS Assignee: kubic-bugs(a)opensuse.org Reporter: pranav.sharma.ama(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- distrobox requires less fiddling with podman / base image, especially to get gui apps to work -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1202983] New: simple-framebuffer error -16 on raspberry pi 4 using latest openSUSE MicroOS RaspberryPi image
by bugzilla_noreply＠suse.com 27 Nov '22

27 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1202983 Bug ID: 1202983 Summary: simple-framebuffer error -16 on raspberry pi 4 using latest openSUSE MicroOS RaspberryPi image Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: MicroOS Assignee: kubic-bugs(a)opensuse.org Reporter: proprietaer1(a)mailbox.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Today I wanted to test MicroOS on my RaspberryPi 4. Unfortunately, the display output stopped during the boot process, with the error: simple-framebuffer.0: [drm] ERROR could not acquire memory range [mem 0x3e3cf000-0x3ebb7fff flags 0x200]: error -16 Steps to reproduce: 1.Download latest MicroOS for RaspberryPi & flash it to sd card. 2.Try to boot the system -- You are receiving this mail because: You are the assignee for the bug.

1 1