- openSUSE Kubic Bugs

[Bug 1190529] [Build 20210914] openQA test fails in podman_image
by bugzilla_noreply＠suse.com 03 May '23

03 May '23

https://bugzilla.suse.com/show_bug.cgi?id=1190529 https://bugzilla.suse.com/show_bug.cgi?id=1190529#c1 Dominique Leuenberger <dimstar(a)opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |WORKSFORME Status|NEW |RESOLVED --- Comment #1 from Dominique Leuenberger <dimstar(a)opensuse.org> --- (In reply to Dominique Leuenberger from comment #0) > ## Further details > > Always latest result in this scenario: > [latest](https://openqa.opensuse.org/tests/ > latest?arch=x86_64&distri=opensuse&flavor=NET&machine=64bit&test=containers_t > w_image_on_ubuntu_host&version=Tumbleweed) This test has been passing reliably for the last three months at least - let's not keep the bug report around (nobody is looking at it anyway) -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1210964] MicroOS does not boot after install on Lenovo ThinkPad X1 Carbon (4th Gen)
by bugzilla_noreply＠suse.com 30 Apr '23

30 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1210964 https://bugzilla.suse.com/show_bug.cgi?id=1210964#c8 Doe <tckkv3bu9k0(a)temp.mailbox.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #8 from Doe <tckkv3bu9k0(a)temp.mailbox.org> --- I've solved the issue. What I did: - changed in the BIOS/UEFI Mode via "Startup ➙ UEFI/Legacy Boot: Both" to "UEFI Only" - boot from USB Media - started the installation process again - noticed minor changes in installation summary, like Update NVRAM: "active" - changed the follwing item: "Systemstart" Secure Boot: "active" => "deactivated" - started the installtion routine - reboot => done; The system re-boots as expected To sum up: After the installation I noticed the new OpenSuse boot screen was coming up on reboot. I guess the installation script wasn't aware of the hybrid UEFI/BIOS setting of my Lenovo Laptop mentioned above and might prepared the System as Legacy BIOS Linux client instead of an UEFI-based one. Which means it doesn't used efibootmgr to write/alter the UEFI boot entry/touch the NVRAM in my case. I had to "force" the installation process to (re-)write the boot entry in the NVRAM, by setting the Firmware to "UEFI-only" mode in the first place. To be clear: My conclusion is based on my observation and extremely "not deep-dive debugging". It could be bloody wrong and I don't want to be rude to the devs or blame your nice upcoming new OS. I just thought that my case could sand down the possible rough edges of the release candidate to make a desktop user's experience as pleasant as possible :) . Have a nice weekend folks! Regards, C. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1210964] MicroOS does not boot after install on Lenovo ThinkPad X1 Carbon (4th Gen)
by bugzilla_noreply＠suse.com 29 Apr '23

29 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1210964 https://bugzilla.suse.com/show_bug.cgi?id=1210964#c7 Richard Brown <rbrown(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rbrown(a)suse.com Priority|P2 - High |P5 - None --- Comment #7 from Richard Brown <rbrown(a)suse.com> --- Resetting priority, as it is a judgement made by individuals who are responsible to resolve the bug. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1210964] MicroOS does not boot after install on Lenovo ThinkPad X1 Carbon (4th Gen)
by bugzilla_noreply＠suse.com 28 Apr '23

28 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1210964 https://bugzilla.suse.com/show_bug.cgi?id=1210964#c6 --- Comment #6 from Thorsten Kukuk <kukuk(a)suse.com> --- I have the same Notebook and that works fine with openSUSE Tumbleweed, which uses the same bootloader configuration. You need UEFI, if you enable or disable secure boot does not matter. But you have to decide before the installation what you want to use: installing with disabled secure boot and enable it later is in general not a good idea, independent of MicroOS or Tumbleweed. (In reply to Doe from comment #5) > Could it be that MicroOS is "made just for UEFI-clients"? No, MicroOS works with all kinds of firmware like Tumbleweed. > I wonder if the Lenovo default value "Legacy/UEFI: both", "Legacy first" > leads to my problem. Could be, I don't remember what the default was. > Should I install MicroOS with secure boot and UEFI-only mode again? MicroOS > seems to use GPT, so in my opinion this kicks out Legacy-Clients with only > BIOS, or am I wrong? GPT has nothing to do with legacy or UEFI firmware. I would suggest to switch to UEFI only, so that no part of the system get's confused and makes a wrong assumption and install new. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1210964] New: MicroOS does not boot after install on Lenovo ThinkPad X1 Carbon (4th Gen)
by bugzilla_noreply＠suse.com 28 Apr '23

28 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1210964 Bug ID: 1210964 Summary: MicroOS does not boot after install on Lenovo ThinkPad X1 Carbon (4th Gen) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: 64bit OS: Other Status: NEW Severity: Major Priority: P5 - None Component: MicroOS Assignee: kubic-bugs(a)opensuse.org Reporter: tckkv3bu9k0(a)temp.mailbox.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 10.0; rv:112.0) Gecko/20100101 Firefox/112.0 Build Identifier: Dear Devs, after I've installed MicroOS on my Lenovo ThinkPad X1 Carbon (4th Gen), it won't boot. The boot menu seems to be a Lenovo one and not GRUB2. It has two tabs, first is called "x" the second does have the Lenovo Diagnostics. When I click on the SUSE boot entry, the screen is black for several seconds and shows the boot menu again. I have to use the MicroOS usb boot media and issue "Boot Linux System" to boot into MicroOS No command in transaction-update menu (bootloader, initrd, grub.cfg) to re-install the bootloader, create grub.cfg or initrd helps to solve my issue. I have no idea to solve this. Reproducible: Always Steps to Reproduce: 1. Boot from MicroOS USB Media 2. Install MicroOS 3. Reboot Actual Results: It does not boot into MicroOS Expected Results: It should boot into the freshly installed MicroOS Basic info about my system: BIOS/UEFI-Settings: UEFI/Legacy Boot :Both CSM-Support: yes lsblk: NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS sda 8:0 0 476.9G 0 disk ├─sda1 8:1 0 8M 0 part └─sda2 8:2 0 476.9G 0 part /usr/local /opt /srv /home /boot/writable /boot/grub2/x86_64-efi /boot/grub2/i386-pc /.snapshots /var /root / sdb 8:16 1 7.6G 0 disk ├─sdb1 8:17 1 4.4M 0 part └─sdb2 8:18 1 3.9G 0 part /run/media/$USER/openSUSE-MicroOS-DVD-x86_64 -- You are receiving this mail because: You are the assignee for the bug.

1 6

[Bug 1210710] New: Including `inxi` in default MicroOS installation
by bugzilla_noreply＠suse.com 22 Apr '23

22 Apr '23

http://bugzilla.suse.com/show_bug.cgi?id=1210710 Bug ID: 1210710 Summary: Including `inxi` in default MicroOS installation 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: groguko36(a)pm.me QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I'm running a Optimus setup (Intel iGPU and Nvidia dGPU). I installed the Nvidia G06 driver with `suse-prime` and `bbswitch`. I had trouble with switching graphic cards. `suse-prime` couldn't detect Intel when I tried to switch to it. Then it would attempt to switch to Nvidia instead and caused black screen with login, because it also couldn't detect Nvidia. The problem is solved by installing the `inxi` package. It seems `inxi` is necessary for detecting running graphic card for `suse-prime`. Therefore, I think `inxi` should come as the default package in MicroOS. -- You are receiving this mail because: You are the assignee for the bug.

1 3

[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 1210483] New: RTL8821CE Firmware not installed on MicroOS
by bugzilla_noreply＠suse.com 20 Apr '23

20 Apr '23

http://bugzilla.suse.com/show_bug.cgi?id=1210483 Bug ID: 1210483 Summary: RTL8821CE Firmware not installed on 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: izineth09(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- OpenSUSE MicroOS does not install the kernel-firmware-realtek package when installing on an HP 14 laptop with RTL8821CE wifi card. Installing the kernel-firmware-realtek-20230320.noarch.rpm package from the installation media manually after installation fixes the issue. -- You are receiving this mail because: You are the assignee for the bug.

1 2

[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