November 2021 - openSUSE Kubic Bugs - openSUSE Mailing Lists

[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 1183582] New: transactional server role has very inconsistent package selection (TW, SLE, Leap)
by bugzilla_noreply＠suse.com 10 Aug '22

10 Aug '22

https://bugzilla.suse.com/show_bug.cgi?id=1183582 Bug ID: 1183582 Summary: transactional server role has very inconsistent package selection (TW, SLE, Leap) Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: MicroOS Assignee: kubic-bugs(a)opensuse.org Reporter: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Selecting the transactional server role results in a very different selection of patterns and packages. On Tumbleweed: https://openqa.opensuse.org/tests/1667896#step/disable_grub_timeout/13 Documentation, Minimal Base, Enhanced Base, AppArmor, YaST Base, Software Management, Minimal Appliance Base On SLE 15 SP3: https://openqa.suse.de/tests/5670408#step/disable_grub_timeout/14 Minimal Base, Enhanced Base, AppArmor, 32-Bit Runtime Environment On Leap 15.3: https://openqa.opensuse.org/tests/1667171#step/disable_grub_timeout/13 Minimal Base, Minimal Appliance Base -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1186158] New: SElinux is blocking socket access for podman
by bugzilla_noreply＠suse.com 04 Apr '22

04 Apr '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1186158 Bug ID: 1186158 Summary: SElinux is blocking socket access for podman Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE MicroOS Status: NEW Severity: Normal Priority: P5 - None Component: MicroOS Assignee: kubic-bugs(a)opensuse.org Reporter: gm.venekamp(a)quicknet.nl QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- test-vm:~ # head -2 /etc/os-release NAME="openSUSE MicroOS" # VERSION="20210515" When starting a container (as root) like traefik, I get the following error: test-vm:~ # podman run -p 8080:8080 -p 80:80 -v /etc/traefik/traefik.yml:/etc/traefik/traefik.yml -v /var/run/podman/podman.sock:/var/run/docker.sock traefik:v2.0 time="2021-05-18T06:46:37Z" level=info msg="Configuration loaded from file: /etc/traefik/traefik.yml" time="2021-05-18T06:46:38Z" level=error msg="Failed to retrieve information of the docker client and server host: Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get http://%2Fvar%2Frun%2Fdocker.sock/v1.24/version: dial unix /var/run/docker.sock: connect: permission denied" providerName=docker This is what /var/log/audit/audit/log tells me: type=AVC msg=audit(1621319586.484:965): avc: denied { connectto } for pid=1785 comm="traefik" path="/run/podman/podman.sock" scontext=system_u:system_r:container_t:s0:c741,c830 tcontext=system_u:system_r:container_runtime_t:s0 tclass=unix_stream_socket permissive=1 test-vm:~ # ll -Z /var/run/podman/podman.sock srw-rw----. 1 root root system_u:object_r:var_run_t:s0 0 May 18 08:46 /var/run/podman/podman.sock Am I doing anything wrong -- You are receiving this mail because: You are the assignee for the bug.

1 11

[Bug 1188957] New: Micro OS Desktop GNOME: Mesa-dri-nouveau not installed on first boot
by bugzilla_noreply＠suse.com 29 Mar '22

29 Mar '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1188957 Bug ID: 1188957 Summary: Micro OS Desktop GNOME: Mesa-dri-nouveau not installed on first boot 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: richwallwork(a)pm.me QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I've installed MicroOS desktop GNOME and noticed that it was reporting that the built in Intel gfx is the graphics adapter rather than the installed Nvidia card (which works fine on regular Tumbleweed). the Journal suggests that nouveau_dri.so cannot be found in /usr/lib64/dri and it seems the Mesa-dri-nouveau package wasn't installed. I used: sudo tukit --continue execute bash zypper in Mesa-dri-nouveau and after a reboot the system is working fine with nouveau. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1183856] New: fstab gets overriden by transactional-update
by bugzilla_noreply＠suse.com 18 Feb '22

18 Feb '22

https://bugzilla.suse.com/show_bug.cgi?id=1183856 Bug ID: 1183856 Summary: fstab gets overriden by transactional-update 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: nmoreychaisemartin(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Running transactional-update removes fstab entries that were added post install Steps to reproduce: - Add fstab entry using transactional-update -c shell - Reboot [ fstab is properly updated ] - Run transactional-update pkg in something - cat /var/lib/overlay/<last overlay>/etc/fstab (or reboot and check fstab) fstab entry is now missing -- You are receiving this mail because: You are the assignee for the bug.

1 5

[Bug 1183521] New: [Build 20210312] openQA test fails in transactional_update
by bugzilla_noreply＠suse.com 18 Feb '22

18 Feb '22

https://bugzilla.suse.com/show_bug.cgi?id=1183521 Bug ID: 1183521 Summary: [Build 20210312] openQA test fails in transactional_update Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/1666862/modules/tran sactional_update/steps/81 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: MicroOS Assignee: iforster(a)suse.com Reporter: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de CC: kubic-bugs(a)opensuse.org Found By: openQA Blocker: Yes Two bugs were observed when running the latest transactional-update on an older Tumbleweed snapshot: 1. "transactional-update" fails in zypper, because /var/lib/rpm inside the new root is an absolute symlink pointing to the current /, which is read-only 2. transactional-update 3.20.0 creates snapshots which transactional-update 2.24.1 does not understand due to a different workdir= value in /etc/fstab ## Observation openQA test in scenario microos-Tumbleweed-MicroOS-Image-ContainerHost-x86_64-container-host-old2microosnext@64bit fails in [transactional_update](https://openqa.opensuse.org/tests/1666862/modules/tra… ## Test suite description Boot from existing, static MicroOS ContainerHost image and transactional-update dup to snapshot under test. ## Reproducible Fails since (at least) Build [20210223](https://openqa.opensuse.org/tests/1644898) ## Expected result Last good: [20210222](https://openqa.opensuse.org/tests/1642729) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=microos… -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1185461] New: ignition doesn't reset firstboot
by bugzilla_noreply＠suse.com 13 Dec '21

13 Dec '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1185461 Bug ID: 1185461 Summary: ignition doesn't reset firstboot 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: lnussel(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Using openSUSE-MicroOS.x86_64-16.0.0-kvm-and-xen-Snapshot20210427.qcow2 in qemu with an ignition config that touches a file in /etc. Rebooting leads to maintenance mode as ignition started again and exists as the file already exist. So for some reason the no firstboot condition is not detected. /boot/writable/firstboot_happened exist though: Entering emergency mode. Exit the shell to continue. Type "journalctl" to view system logs. You might want to save "/run/initramfs/rdsosreport.txt" to a USB stick or /boot after mounting them and attach it to a bug report. Press Enter for maintenance (or press Control-D to continue): :/root# mount -o subvol=@/boot/writable /dev/vda3 /mnt :/root# ls /mnt/ firstboot_happened :/root# cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-5.11.16-1-default root=UUID=1bd1020f-74e9-4d1f-bb36-859e1f4e86bd rw rd.timeout=60 quiet systemd.show_status=yes console=ttyS0,115200 console=tty0 net.ifnames=0 ignition.firstboot ignition.platform.id=qemu -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 1187313] New: selinux-policy-targeted breaks StandardOutput=tty
by bugzilla_noreply＠suse.com 02 Dec '21

02 Dec '21

https://bugzilla.suse.com/show_bug.cgi?id=1187313 Bug ID: 1187313 Summary: selinux-policy-targeted breaks StandardOutput=tty Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de CC: kubic-bugs(a)opensuse.org Found By: --- Blocker: --- Services with StandardOutput=tty (like MicroOS-Firstboot) fail to start when the targeted policy is enforced: Jun 11 13:57:05 f195.suse.de systemd[1183]: MicroOS-firstboot.service: Failed to set up standard input: Permission denied Jun 11 13:57:05 f195.suse.de kernel: audit: type=1400 audit(1623419825.264:7): avc: denied { watch watch_reads } for pid=1183 comm="(irstboot)" path="/dev/console" dev="devtmpfs" ino=12 scontext=system_u:system_r:init_t:s0 tcontext=system_u:object_r:console_device_t:s0 tclass=chr_file permissive=0 Jun 11 13:57:05 f195.suse.de systemd[1183]: MicroOS-firstboot.service: Failed at step STDIN spawning /usr/libexec/MicroOS-firstboot: Permission denied The Fedora policy allows that for TTYs, so should probably do the same for console_device_t: https://github.com/fedora-selinux/selinux-policy/commit/f4a7e3a562499916c83… -- You are receiving this mail because: You are on the CC list for the bug.

1 13

[Bug 1188932] New: SELinux prevents systemd-firstboot
by bugzilla_noreply＠suse.com 29 Nov '21

29 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1188932 Bug ID: 1188932 Summary: SELinux prevents systemd-firstboot 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: kukuk(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- With active SELinux systemd-firstboot doesn't work: Fri 2021-07-30 13:54:16 UTC init.scope[1]: Starting First Boot Wizard... Fri 2021-07-30 13:54:16 UTC systemd-firstboot.service[560]: systemd-firstboot.service: Failed to set up standard input: Permission denied Fri 2021-07-30 13:54:16 UTC systemd-firstboot.service[560]: systemd-firstboot.service: Failed at step STDIN spawning systemd-firstboot: Permission denied Fri 2021-07-30 13:54:16 UTC init.scope[1]: systemd-firstboot.service: Main process exited, code=exited, status=208/STDIN Fri 2021-07-30 13:54:16 UTC init.scope[1]: systemd-firstboot.service: Failed with result 'exit-code'. Fri 2021-07-30 13:54:16 UTC init.scope[1]: Failed to start First Boot Wizard. Fri 2021-07-30 13:54:16 UTC kernel: audit: type=1400 audit(1627653256.048:3): avc: denied { watch watch_reads } for pid=560 comm="(irstboot)" path="/dev/console" dev="devtmpfs" ino=12 scontext=system_u:system_r:init_t:s0 tcontext=system_u:object_r:console_device_t:s0 tclass=chr_file permissive=0 -- You are receiving this mail because: You are the assignee for the bug.

1 3

[kubic-bugs] [Bug 1153687] New: Zypper repo name detection broken
by bugzilla_noreply＠novell.com 24 Nov '21

24 Nov '21

http://bugzilla.suse.com/show_bug.cgi?id=1153687 Bug ID: 1153687 Summary: Zypper repo name detection broken Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kubic Assignee: kubic-bugs(a)opensuse.org Reporter: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- zypper ar obs://some:where/ results in a URL such as https://download.opensuse.org/repositories/some:/where/openSUSE-MicroOS-201… -- You are receiving this mail because: You are the assignee for the bug.

2 16

[Bug 1192976] intermittent log spam about i2c failure on raspberry Pi 3B
by bugzilla_noreply＠suse.com 23 Nov '21

23 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192976 Thorsten Kukuk <kukuk(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|MicroOS |Kernel Assignee|kubic-bugs(a)opensuse.org |kernel-bugs(a)opensuse.org -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1188110] New: pkcon system-upgrade leads to unbootable system with kernel upgrade
by bugzilla_noreply＠suse.com 23 Nov '21

23 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1188110 Bug ID: 1188110 Summary: pkcon system-upgrade leads to unbootable system with kernel upgrade 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: alois1(a)gmx-topmail.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I recently installed MicroOS Desktop KDE. I attempted to upgrade this system from 20210704 to 20210706 using pkcon, which included a kenel upgrade to 5.13. This upgrade lead to an unbootable system with the following symptoms: * In the GRUB menu, it is attempted to load the wrong kernel version (5.12.13). * When manually editing the kernel and initrd version to 5.13.0, the initrd enters emergency mode after some delay. * Further investigation shows that initrd is incomplete and lacks at least crypttab, so the partitions on the encrypted disks cannot be mounted and caused the timeout. The issue is reproducible, after rolling back to the last snapshot on 20210704 and attempting the upgrade again the symptoms are the same. I have for now upgraded the system using zypper dup inside tukit. This lead to a working upgraded system. -- You are receiving this mail because: You are the assignee for the bug.

1 14

[Bug 1192976] New: intermittent log spam about i2c failure on raspberry Pi 3B
by bugzilla_noreply＠suse.com 23 Nov '21

23 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1192976 Bug ID: 1192976 Summary: intermittent log spam about i2c failure on raspberry Pi 3B Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: MicroOS Assignee: kubic-bugs(a)opensuse.org Reporter: bertocheraphael(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 853945 --> http://bugzilla.opensuse.org/attachment.cgi?id=853945&action=edit possibly relevant was an occasional page allocation failure I am really clueless as to what causes this, couldn't yet figure by looking at previous logs; When it starts it goes out like the following: Nov 15 11:24:53 localhost kernel: i2c-bcm2835 3f805000.i2c: i2c transfer timed out Nov 15 11:25:04 localhost kernel: i2c-bcm2835 3f805000.i2c: i2c transfer timed out Nov 15 11:25:05 localhost kernel: i2c-bcm2835 3f805000.i2c: i2c transfer timed out Nov 15 11:25:16 localhost kernel: i2c-bcm2835 3f805000.i2c: i2c transfer timed out Nov 15 11:25:28 localhost kernel: i2c-bcm2835 3f805000.i2c: i2c transfer timed out Nov 15 11:25:29 localhost kernel: i2c-bcm2835 3f805000.i2c: i2c transfer timed out Nov 15 11:25:40 localhost kernel: i2c-bcm2835 3f805000.i2c: i2c transfer timed out Nov 15 11:25:52 localhost kernel: i2c-bcm2835 3f805000.i2c: i2c transfer timed out Nov 15 11:25:53 localhost kernel: i2c-bcm2835 3f805000.i2c: i2c transfer timed out Nov 15 11:26:04 localhost kernel: i2c-bcm2835 3f805000.i2c: i2c transfer timed out In this particular case the host was mostly idle and the latest log message preceding the errors happened 42 seconds before and it was a very low intensity [Info]. It usually starts after some hours after the SoC has booted and then sticks until the next reboot at that rate. The only other issue I saw on the log I considered possibly relevant was an occasional page allocation failure showing at pageallocationfailure.txt:185. The only devices attached to the Raspberry are the SD card, an USB flash drive and the Ethernet cable, and occasionally a case fan. There these two related project issues are similar similar bug in some random repository but nothing I tried from there seemed to fix it. https://github.com/raspberrypi/linux/issues/3064 https://github.com/PiSupply/PiJuice/issues/634 It's currently running VERSION_ID="20211117" with only default repos which are oss and update. Linux localhost 5.14.14-3-default #1 SMP Thu Oct 21 05:05:03 UTC 2021 (2b5383f) aarch64 aarch64 aarch64 GNU/Linux What else can I provide? Have a good one -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192619] New: Kubicctl doesn't work work transactional_update executor
by bugzilla_noreply＠suse.com 19 Nov '21

19 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1192619 Bug ID: 1192619 Summary: Kubicctl doesn't work work transactional_update executor Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kubic Assignee: kubic-bugs(a)opensuse.org Reporter: adathor(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 853710 --> http://bugzilla.opensuse.org/attachment.cgi?id=853710&action=edit kubicctl_error Hi, I've installed a small Kubic cluster with 1 control-plane and 2 worker nodes (4vCPU, 4GB ram in libvirt) and when I try to add the nodes with `kubicctl` it simply fails to do so with the attached kubicctl_error.log message. I took the kubeadm that salt cmd from the master tries to execute on the worker, ran it on the minion manually and immediately was added: ``` kubeadm join 172.168.150.25:6443 --token deu47v.pad0gfatrn2g6sfh --discovery-token-ca-cert-hash sha256:1715bf3bb55d24abbba682b4cdc0482c9c77bf1003c8fa2a305fcc48c0fbd4ca ``` Some further investigation revealed that if the `transactional_update` executor module is disabled in salt-minion on the worker, kubicctl is able to add the nodes. I also tried to run the `kubeadm join cmd` on the worker in `t-u shell` I get the same error what `kubicctl` was throwing at first (kubicctl_error.log). (Tested on 2 separate system libvirt and ESXI. Also had this issue running on the Kubic mailing list: https://lists.opensuse.org/archives/list/kubic@lists.opensuse.org/thread/GU…) Let me know if you need additional information/testing from my side! Br, A. -- You are receiving this mail because: You are the assignee for the bug.

1 6

[Bug 1192619] Kubicctl doesn't work work transactional_update executor
by bugzilla_noreply＠suse.com 19 Nov '21

19 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192619 https://bugzilla.suse.com/show_bug.cgi?id=1192619#c6 Thorsten Kukuk <kukuk(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #6 from Thorsten Kukuk <kukuk(a)suse.com> --- Fixed. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192828] New: k3s 1.22.3+k3s1: subcommand crictl doesn't work
by bugzilla_noreply＠suse.com 18 Nov '21

18 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192828 Bug ID: 1192828 Summary: k3s 1.22.3+k3s1: subcommand crictl doesn't work Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kubic Assignee: kubic-bugs(a)opensuse.org Reporter: dheidler(a)suse.com QA Contact: qa-bugs(a)suse.de CC: guillaume.gardet(a)opensuse.org Found By: --- Blocker: --- # k3s crictl No help topic for 'crictl' But when using the k3s binary from https://github.com/k3s-io/k3s/releases/tag/v1.22.3+k3s1 the same command works fine. -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1192698] New: libvirtd internal error
by bugzilla_noreply＠suse.com 18 Nov '21

18 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1192698 Bug ID: 1192698 Summary: libvirtd internal error Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Critical Priority: P5 - None Component: MicroOS Assignee: kubic-bugs(a)opensuse.org Reporter: fjlee93(a)outlook.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Installed libvirt and kvm package via kvm_server kvm_tools patterns. Able to start and enable service but get the following errors in libvirtd systemd logs: Internal error: The provided value contains invalid characters: N/A Internal error: Field value contains invalid characters Still able to connect to the kvm via Virt-Manager but, when creating virtual machines this error comes up: Unsupported configuration: USB redirection is not supported by this version of QEMU -- You are receiving this mail because: You are the assignee for the bug.

1 6

[Bug 1192600] Package Version missmatch from OBS and Download Repository
by bugzilla_noreply＠suse.com 12 Nov '21

12 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192600 https://bugzilla.suse.com/show_bug.cgi?id=1192600#c2 Thorsten Kukuk <kukuk(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #2 from Thorsten Kukuk <kukuk(a)suse.com> --- (In reply to Enno Gotthold from comment #0) > In the OBS at openSUSE:Factory there is version 1.22.3+k3s1 built but at > download.o.o there is for days now only version 1.21.3+k3s1 available. > > I haven't checked with more packages but this is the one where I found a > mismatch. You will find a lot of mismatches. That packages will be accepted in openSUSE:Factory does not mean they are immediately available, only with the next released snapshot. And if this snapshot does not pass QA for whatever reasons, it can take quite some time until you see them on download.o.o -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192600] New: Package Version missmatch from OBS and Download Repository
by bugzilla_noreply＠suse.com 11 Nov '21

11 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1192600 Bug ID: 1192600 Summary: Package Version missmatch from OBS and Download Repository 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: egotthold(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- In the OBS at openSUSE:Factory there is version 1.22.3+k3s1 built but at download.o.o there is for days now only version 1.21.3+k3s1 available. I haven't checked with more packages but this is the one where I found a mismatch. [1]: https://build.opensuse.org/package/show/openSUSE:Factory/k3s [2]: https://build.opensuse.org/package/binaries/openSUSE:Factory/k3s/standard [3]: https://download.opensuse.org/tumbleweed/repo/oss/x86_64/k3s-1.21.3+k3s1-1.… I checked in mirrorcache as well and there it also says that this is the most up-to-date version: [4]: https://mirrorcache-eu.opensuse.org/tumbleweed/repo/oss/x86_64/k3s-1.21.3+k… -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1192242] New: transactional-update 3.6.0 do not correctly mount /etc inside the snapshot
by bugzilla_noreply＠suse.com 11 Nov '21

11 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1192242 Bug ID: 1192242 Summary: transactional-update 3.6.0 do not correctly mount /etc inside the snapshot 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: aplanas(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Using a fresh microos installation (or an updated one) with t-u 3.6.0, when a package try to install configuration files in /etc, the files are not sync back into the current /etc and the overlay get lost: # transactional-update pkg in salt-minion (This will create some config files in /etc/salt) # ls -la /etc/salt ls: cannot access '/etc/salt': No such file or directory # mount ... overlay on /etc type overlay (rw,relatime,seclabel,lowerdir=/sysroot/etc,upperdir=/sysroot/var/lib/overlay/1/etc,workdir=/sysroot/var/lib/overlay/work-etc) ... But the overlay is there: # ls /var/lib/overlay/ 1 3 transactional-update.newsnapshot work-etc # ls /var/lib/overlay/3/salt ... # cat /etc/fstab ... UUID=3de12086-e4a4-4770-b4d5-c19a22ccdab4 /var btrfs defaults,x-initrd.mount 0 0 overlay /etc overlay defaults,lowerdir=/sysroot/etc,upperdir=/sysroot/var/lib/overlay/1/etc,workdir=/sysroot/var/lib/overlay/work-etc,x-systemd.requires-mounts-for=/var,x-systemd.requires-mounts-for=/sysroot/var,x-initrd.mount 0 0 A shell shows the pending changes in etc, mounting the overlay: # transactional-update -c -d shell # ls /etc/salt ... And a touch in /etc seems to trigger the rsync: # touch /etc/changed # exit ... rsync: [receiver] rsync_xal_set: lremovexattr("/etc/.","security.selinux") failed: Permission denied (13) ... rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1330) [sender=3.2.3] 2021-11-02 10:09:00 Discarding snapshot 4. ERROR: `rsync --archive --inplace --xattrs --acls --exclude 'fstab' --delete --quiet '/.snapshots/4/snapshot/etc/' /etc` returned with error code 23. transactional-update finished -- You are receiving this mail because: You are the assignee for the bug.

1 9

[Bug 1192307] New: Missing tukit.conf documentation
by bugzilla_noreply＠suse.com 03 Nov '21

03 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1192307 Bug ID: 1192307 Summary: Missing tukit.conf documentation 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: aplanas(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- tukit.conf have options that are useful for users, like BINDDIR. We should document them. -- You are receiving this mail because: You are the assignee for the bug.

1 1