January 2023 - 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 1206946] New: First boot fails with USB devices plugged in
by bugzilla_noreply＠suse.com 19 Apr '23

19 Apr '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1206946 Bug ID: 1206946 Summary: First boot fails with USB devices plugged in 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: sebastian.kuebbeler(a)gmx.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:108.0) Gecko/20100101 Firefox/108.0 Build Identifier: I am trying to install MicroOS on a Raspberry Pi, but it fails when non-simple USB devices are attached. I used this image: openSUSE-MicroOS.aarch64-16.0.0-ContainerHost-RaspberryPi-Snapshot20230101.raw.xz I double checked this against the latest Tumbleweed image: openSUSE-Tumbleweed-ARM-JeOS-raspberrypi.aarch64-2022.12.31-Snapshot20230101.raw.xz I also tested with the latest Leap image: openSUSE-Leap-15.4-ARM-JeOS-raspberrypi.aarch64-2022.09.29-Build31.38.raw.xz The Leap Image works, so it must be an issue with Tumbleweed. Reproducible: Always Steps to Reproduce: 1. Boot 2. Enters UBoot 3. Reboots -> Loop Actual Results: Failed to boot Expected Results: Should boot -- You are receiving this mail because: You are the assignee for the bug.

1 5

[Bug 1206277] New: Network document scanners do not work out of the box
by bugzilla_noreply＠suse.com 19 Apr '23

19 Apr '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1206277 Bug ID: 1206277 Summary: Network document scanners do not work out of the box 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: vortex(a)z-ray.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hello there I found out that network attached document scanners do not work on MicroOS out of the box. For my Canon TR4550 2 in 1 printer I had to add the following packages to make this workload work: - simple-scan (it's not on flathub) - sane-backends Then I configured sane to also use escl for network attached scanners to work by uncommenting the line: #escl in /etc/sane.d/dll.conf After a reboot simpel-scan was able to detect my network printer and successfully scanned the printer test page. I'd like to ask if this can be added to the base MicroOS image? Kind regards, V. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1205108] New: Redundant program for system monitoring on Gnome
by bugzilla_noreply＠suse.com 11 Feb '23

11 Feb '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1205108 Bug ID: 1205108 Summary: Redundant program for system monitoring on Gnome 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: scribble3299(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:106.0) Gecko/20100101 Firefox/106.0 Build Identifier: There are two programs installed by default on Gnome in Micro OS fresh install, Gnome System Monitor and Gnome Usage Respectively. Reproducible: Always Steps to Reproduce: 1.Install Micro OS Desktop Gnome 2.Open App Menu Actual Results: Two system monitor program installed with almost the same functionality. Expected Results: Gnome System Monitor(GSM) should be the only installed program for system monitoring as it is more feature rich and functional as compared to Gnome Usage which seems to be the "lite" version of GSM -- You are receiving this mail because: You are the assignee for the bug.

1 6

[Bug 1207726] New: Micro OS First Boot Fails to install Firefox on AARCH64
by bugzilla_noreply＠suse.com 30 Jan '23

30 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1207726 Bug ID: 1207726 Summary: Micro OS First Boot Fails to install Firefox on AARCH64 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: openSUSE Tumbleweed Status: NEW Severity: Critical Priority: P5 - None Component: MicroOS Assignee: kubic-bugs(a)opensuse.org Reporter: eric(a)tuxbot.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- When logging into Micro OS Gnome RC after creating a user the 'First Boot' script runs [/usr/bin/mod-firstboot] and attempts to install org.mozilla.firefox. However this always fails on aarch64 as Mozilla only provides an x86_64 package of the Firefox flatpak. This results in the mod-firstboot script failing with an error on every login. This also results in a broken environment as the rest of mod-firstboot fails to run. I don't know a lot about Micro OS but would suggest improving mod-firstboot in the following ways. 1) Install Firefox last and not first. This will allow the other components to successfully install even if the Firefox flatpack fails. 2) For AARCH64 default to installing a different brower, the org.chromium.Chromium flatpak is working well for me on AARCH64. Or even better help/convince/persuade Mozilla to address * https://bugzilla.mozilla.org/show_bug.cgi?id=1646462 * https://bugzilla.mozilla.org/show_bug.cgi?id=1677963 -- You are receiving this mail because: You are the assignee for the bug.

1 5

[Bug 1181547] [Build 20210128] openQA test fails in journal_check
by bugzilla_noreply＠suse.com 25 Jan '23

25 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1181547 https://bugzilla.suse.com/show_bug.cgi?id=1181547#c3 Guillaume GARDET <guillaume.gardet(a)arm.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #3 from Guillaume GARDET <guillaume.gardet(a)arm.com> --- https://openqa.opensuse.org/tests/3064554 looks good now. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1207509] New: [Build 20230124] buildah is not happy with the etc/containers/storage.conf
by bugzilla_noreply＠suse.com 25 Jan '23

25 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1207509 Bug ID: 1207509 Summary: [Build 20230124] buildah is not happy with the etc/containers/storage.conf Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/3066635/modules/buil dah/steps/73 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: MicroOS Assignee: kubic-bugs(a)opensuse.org Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: openQA Blocker: Yes ## Observation [33mWARN[0m[0000] Failed to decode the keys ["storage.driver_priority"] from "/etc/containers/storage.conf" [31mERRO[0m[0000] The storage 'driver' option must be set in /etc/containers/storage.conf to guarantee proper operation Issue was introduced with https://build.opensuse.org/request/show/1060361#tab-pane-changes +- storage.conf: Unset 'driver' and set 'driver_priority' to + allow podman to use 'btrfs' if available and fallback to + 'overlay' if not. openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-containers_host_podman@64bit fails in [buildah](https://openqa.opensuse.org/tests/3066635/modules/buildah/steps/73) ## Test suite description Maintainer: dheidler. Extra tests about CLI software in container module ## Reproducible Fails since (at least) Build [20230124](https://openqa.opensuse.org/tests/3066155) ## Expected result Last good: [20230123](https://openqa.opensuse.org/tests/3063296) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=opensus… -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1175850] User mount option 'x-initrd.mount' vanishes during initrd transitions
by bugzilla_noreply＠suse.com 24 Jan '23

24 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1175850 Bug 1175850 depends on bug 1198731, which changed state. Bug 1198731 Summary: libmount: when moving a mounted tree, all mounted sub tree entries in utab should also be updated https://bugzilla.suse.com/show_bug.cgi?id=1198731 What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1199051] [Build 20220430] dracut - post trans failure
by bugzilla_noreply＠suse.com 19 Jan '23

19 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1199051 https://bugzilla.suse.com/show_bug.cgi?id=1199051#c11 David Cassany <dcassany(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |FIXED --- Comment #11 from David Cassany <dcassany(a)suse.com> --- Closing as fixed, the upstream fix is available since kiwi v9.24.41, current TW version is already v9.24.55 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[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