April 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 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

[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

[kubic-bugs] [Bug 1085619] New: Softlockup with btrfs and kubic (CaaSP on openSUSE)
by bugzilla_noreply＠novell.com 16 Sep '21

16 Sep '21

http://bugzilla.suse.com/show_bug.cgi?id=1085619 Bug ID: 1085619 Summary: Softlockup with btrfs and kubic (CaaSP on openSUSE) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Kubic Assignee: jeffm(a)suse.com Reporter: kukuk(a)suse.com QA Contact: qa-bugs(a)suse.de CC: kubic-bugs(a)opensuse.org, lpechacek(a)suse.com Found By: --- Blocker: --- With current openSUSE Kubic builds (CaaSP based on openSUSE Tumbleweed), we seem to run into the same issue as with CaaSP v1: bsc#1041296 - admin node freezes - no shell after putting password into login prompt Could it be that the fixes are missing in the upstream kernel? -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1182544] New: transactional-update fails when self-updating from old snapshot
by bugzilla_noreply＠suse.com 28 Jun '21

28 Jun '21

https://bugzilla.suse.com/show_bug.cgi?id=1182544 Bug ID: 1182544 Summary: transactional-update fails when self-updating from old snapshot Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/1638401/modules/imag e_checks/steps/13 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: dimstar(a)opensuse.org, kubic-bugs(a)opensuse.org Found By: openQA Blocker: Yes This test boots into an old MicroOS image. It fails because combustion failed to run, which is caused by transactional-updates self update: Feb 21 05:49:26.233585 localhost combustion[542]: New version found - updating... Feb 21 05:49:26.374352 localhost combustion[703]: Loading repository data... Feb 21 05:49:26.584979 localhost combustion[703]: Reading installed packages... Feb 21 05:49:26.884304 localhost combustion[703]: Retrieving package transactional-update-3.1.4-1.1.x86_64 (1/1), 54.6 KiB ( 73.1 KiB unpacked) Feb 21 05:49:27.121761 localhost combustion[703]: .........done] Feb 21 05:49:27.306095 localhost combustion[742]: Loading repository data... Feb 21 05:49:27.517683 localhost combustion[742]: Reading installed packages... Feb 21 05:49:27.771859 localhost combustion[742]: Retrieving package libtukit0-3.1.4-1.1.x86_64 (1/2), 128.4 KiB (283.7 KiB unpacked) Feb 21 05:49:28.000220 localhost combustion[742]: ..........done] Feb 21 05:49:28.002964 localhost combustion[742]: Retrieving package tukit-3.1.4-1.1.x86_64 (2/2), 55.9 KiB ( 85.2 KiB unpacked) Feb 21 05:49:28.148466 localhost combustion[742]: ......done] Feb 21 05:49:28.209932 localhost combustion[741]: /tmp/transactional-update.a1AVPfXW9o/usr/sbin/tukit: /lib64/libselinux.so.1: no version information available (required by /tmp/transactional-update.a1AVPfXW9o/usr/lib64/libtukit.so.0) Feb 21 05:49:28.215355 localhost combustion[542]: transactional-update 3.1.4 started Feb 21 05:49:28.217252 localhost combustion[542]: Options: shell Feb 21 05:49:28.271971 localhost combustion[542]: Separate /var detected. Feb 21 05:49:28.320210 localhost combustion[741]: tukit: /lib64/libselinux.so.1: no version information available (required by /tmp/transactional-update.a1AVPfXW9o/usr/lib64/libtukit.so.0) Feb 21 05:49:28.328102 localhost combustion[741]: Failure (dbus fatal exception). ... Feb 21 05:49:29.012290 localhost combustion[741]: ERROR: filesystem error: cannot copy: File exists [/run/netconfig] [/.snapshots/2/snapshot/run/netconfig] Feb 21 05:49:29.013155 localhost combustion[542]: Opening chroot in snapshot , continue with 'exit' Feb 21 05:49:29.013981 localhost combustion[877]: tukit: /lib64/libselinux.so.1: no version information available (required by /tmp/transactional-update.a1AVPfXW9o/usr/lib64/libtukit.so.0) Feb 21 05:49:29.015824 localhost combustion[877]: 2021-02-21 05:49:29 tukit 3.1.4 started ... ## Observation openQA test in scenario microos-Tumbleweed-MicroOS-Image-x86_64-microos-old2microosnext@64bit fails in [image_checks](https://openqa.opensuse.org/tests/1638401/modules/image_check… ## Test suite description Boot from existing, static MicroOS image and transactional-update dup to snapshot under test ## Reproducible Fails since (at least) Build [20210219](https://openqa.opensuse.org/tests/1636750) ## Expected result Last good: [20210218](https://openqa.opensuse.org/tests/1635223) (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 1153687] Zypper repo name detection broken
by bugzilla_noreply＠suse.com 29 Apr '21

29 Apr '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1153687 http://bugzilla.opensuse.org/show_bug.cgi?id=1153687#c16 Michael Andres <ma(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution|--- |FIXED Flags|needinfo?(adrian.schroeter@ | |suse.com) | --- Comment #16 from Michael Andres <ma(a)suse.com> --- Will be in zypper-1.14.44 (now in git:master; submitted to TW today or tomorrow) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1172656] MicroOS Desktop: Wired network requires root password
by bugzilla_noreply＠suse.com 29 Apr '21

29 Apr '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1172656 http://bugzilla.opensuse.org/show_bug.cgi?id=1172656#c6 Richard Brown <rbrown(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |rbrown(a)suse.com Resolution|--- |FIXED --- Comment #6 from Richard Brown <rbrown(a)suse.com> --- No response, but assumed resolved -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1153687] Zypper repo name detection broken
by bugzilla_noreply＠suse.com 29 Apr '21

29 Apr '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1153687 http://bugzilla.opensuse.org/show_bug.cgi?id=1153687#c15 Richard Brown <rbrown(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|rbrown(a)suse.com |ma(a)suse.com --- Comment #15 from Richard Brown <rbrown(a)suse.com> --- Fixing assignment, MA is dealing with this -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1177487] cockpit-ws image is unusable
by bugzilla_noreply＠suse.com 29 Apr '21

29 Apr '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1177487 http://bugzilla.opensuse.org/show_bug.cgi?id=1177487#c2 Richard Brown <rbrown(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |amajer(a)suse.com --- Comment #2 from Richard Brown <rbrown(a)suse.com> --- Still doesn't work, but now fails with a different error podman container runlabel --name cockpit-ws RUN registry.opensuse.org/opensuse/cockpit-ws openSUSE Tumbleweed 20210423 + HA Error: repository name must be lowercase Error: `/proc/self/exe run -d --name NAME --privileged --pid=host -v /:/host IMAGE /container/atomic-run --local-ssh` failed: exit status 125 Any suggestions? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1179453] New: [Build 51.1_15.3][MicroOS] Unknown group 'render' in 50-udev-default.rules
by bugzilla_noreply＠suse.com 29 Apr '21

29 Apr '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1179453 Bug ID: 1179453 Summary: [Build 51.1_15.3][MicroOS] Unknown group 'render' in 50-udev-default.rules Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: x86-64 URL: https://openqa.suse.de/tests/5078838/modules/journal_c heck/steps/20 OS: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: MicroOS Assignee: kubic-bugs(a)opensuse.org Reporter: ioannis.bonatakis(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: openQA Blocker: Yes ## Observation /usr/lib/udev/rules.d/50-udev-default.rules contains ``` SUBSYSTME=="kfd", GROUP="render",MODE="0666" ``` but this group does not exists ``` root:x:0:[m shadow:x:15:[m trusted:x:42:[m users:x:100:[m messagebus:x:499:[m nogroup:x:65533:nobody[m nobody:x:65534:[m wheel:x:498:[m kmem:x:497:[m lock:x:496:[m tty:x:5:[m utmp:x:495:[m audio:x:494:[m cdrom:x:493:[m dialout:x:492:[m disk:x:491:[m input:x:490:[m kvm:x:489:[m lp:x:488:[m tape:x:487:[m video:x:486:[m systemd-journal:x:485:[m systemd-network:x:484:[m systemd-resolve:x:483:[m systemd-timesync:x:482:[m systemd-coredump:x:481:[m sshd:x:480:[m chrony:x:479:[m ``` The output from the journal reports `localhost systemd-udevd[221]: /usr/lib/udev/rules.d/50-udev-default.rules:40 Unknown group 'render', ignoring` openQA test in scenario microos-5.0-DVD-x86_64-suse_microos_autoyast@64bit fails in [journal_check](https://openqa.suse.de/tests/5078838/modules/journal_check/steps/20) ## Test suite description ## Reproducible Fails since (at least) Build [49.1_13.7](https://openqa.suse.de/tests/5032758) ## Expected result Last good: (unknown) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.suse.de/tests/latest?arch=x86_64&distri=microos&flavor=DVD&machine=64bit&test=suse_microos_autoyast&version=5.0) -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1182199] New: Flatpack Chromium not starting via x-scheme-handler/https
by bugzilla_noreply＠suse.com 29 Apr '21

29 Apr '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1182199 Bug ID: 1182199 Summary: Flatpack Chromium not starting via x-scheme-handler/https Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: MicroOS Assignee: kubic-bugs(a)opensuse.org Reporter: buxel.dev(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Wen clicking a link in any application (not a browser), the application picker asks, which application to launch. If chromium is selected, nothing happens. Steps to reproduce - Install MocroOS KDE - Install Chromium flatpack - Click link on any application to trigger x-scheme-handler/https - select chromium to open Expected result: chrome opens the url Actual result: nothing happens Additional observation: chromium is not recognized as default browser Solution: install xdg-desktop-portal-gtk - should this be part of the KDE pattern? -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 1182544] transactional-update fails when self-updating from old snapshot
by bugzilla_noreply＠suse.com 29 Apr '21

29 Apr '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1182544 http://bugzilla.opensuse.org/show_bug.cgi?id=1182544#c9 Richard Brown <rbrown(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #9 from Richard Brown <rbrown(a)suse.com> --- It's been fixed -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1183231] [Staging J] YaST is not installing microos_base_zypper pattern for container host role, causing OpenQA test failures
by bugzilla_noreply＠suse.com 29 Apr '21

29 Apr '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1183231 http://bugzilla.opensuse.org/show_bug.cgi?id=1183231#c4 Richard Brown <rbrown(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |rbrown(a)suse.com Resolution|--- |FIXED --- Comment #4 from Richard Brown <rbrown(a)suse.com> --- It's been fixed -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1183521] [Build 20210312] openQA test fails in transactional_update
by bugzilla_noreply＠suse.com 29 Apr '21

29 Apr '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1183521 http://bugzilla.opensuse.org/show_bug.cgi?id=1183521#c2 Richard Brown <rbrown(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |rbrown(a)suse.com Resolution|--- |FIXED --- Comment #2 from Richard Brown <rbrown(a)suse.com> --- It's been fixed -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1184037] New: MicroOS Desktop with GNOME is now in Beta
by bugzilla_noreply＠suse.com 29 Apr '21

29 Apr '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1184037 Bug ID: 1184037 Summary: MicroOS Desktop with GNOME is now in Beta 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: ngompa13(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- With the changes that have been done for this HackWeek, the openSUSE MicroOS Desktop is now ready to move from "ALPHA" to "BETA" status. Let's make that effective to the user now. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1183582] transactional server role has very inconsistent package selection (TW, SLE, Leap)
by bugzilla_noreply＠suse.com 29 Apr '21

29 Apr '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1183582 http://bugzilla.opensuse.org/show_bug.cgi?id=1183582#c1 Richard Brown <rbrown(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rbrown(a)suse.com --- Comment #1 from Richard Brown <rbrown(a)suse.com> --- Indeed it does.. If you'd like my opinion: Tumbleweed should not have YaST and Software Management SLE/Leap should have Documentation and Minimal Appliance Base SLE/Leap should not have 32-bit Runtime Environment But none of this is a Component MicroOS bug and I won't be submitting the above proposed change - my preference would be to drop the Transactional Server system role. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1183894] New: MicroOS needs to no longer ship AppArmor
by bugzilla_noreply＠suse.com 29 Apr '21

29 Apr '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1183894 Bug ID: 1183894 Summary: MicroOS needs to no longer ship AppArmor 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: ngompa13(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- All openSUSE MicroOS variants are no longer going to be shipping AppArmor and will exclusively use SELinux. This bug is the reference for making this change in all the various things. -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1184411] Opening polari flatpak crashes packagekitd and makes gnome go back to login screen
by bugzilla_noreply＠suse.com 29 Apr '21

29 Apr '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1184411 http://bugzilla.opensuse.org/show_bug.cgi?id=1184411#c1 Richard Brown <rbrown(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mpdesouza(a)suse.com, | |rbrown(a)suse.com Flags| |needinfo?(mpdesouza(a)suse.co | |m) --- Comment #1 from Richard Brown <rbrown(a)suse.com> --- Are you sure this is a MicroOS bug? on the surface it looks like an issue with the upstream Polari to me. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1185463] New: kdump fails on microos
by bugzilla_noreply＠suse.com 29 Apr '21

29 Apr '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1185463 Bug ID: 1185463 Summary: kdump fails 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: lnussel(a)suse.com QA Contact: qa-bugs(a)suse.de CC: db7532(a)qq.com, ptesarik(a)suse.com Found By: --- Blocker: --- kdump is installed by default on microos and fails always. # head -2 /etc/os-release NAME="openSUSE MicroOS" # VERSION="20210427" # journalctl|grep kdump [...] Apr 29 07:41:18 dhcp144 systemd[1]: Starting Load kdump kernel and initrd... Apr 29 07:41:18 dhcp144 load.sh[1147]: No kdump initial ramdisk found. Tried to locate /boot/initrd-5.11.16-1-default-kdump. Apr 29 07:41:18 dhcp144 systemd[1]: kdump.service: Main process exited, code=exited, status=6/NOTCONFIGURED Apr 29 07:41:18 dhcp144 systemd[1]: kdump.service: Failed with result 'exit-code'. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1184385] firewalld missing in installer/installation image for MicroOS Desktop
by bugzilla_noreply＠suse.com 29 Apr '21

29 Apr '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1184385 http://bugzilla.opensuse.org/show_bug.cgi?id=1184385#c2 Richard Brown <rbrown(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |rbrown(a)suse.com Resolution|--- |WONTFIX --- Comment #2 from Richard Brown <rbrown(a)suse.com> --- firewalld is not supported on MicroOS for a multitude of reasons Any firewall interferes with container iptables rules. On the MicroOS desktop there is no valid usecase for having a firewall, as their shouldn't be any user installed services opening ports anyhow. I consider it a bug that YaST offers a firewall on the security section of the YaST Installation settings, the requirement for MicroOS was only that the security section allow the management of SELinux/AppArmor. Closing as WONTFIX -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1184385] firewalld missing in installer/installation image for MicroOS Desktop
by bugzilla_noreply＠suse.com 29 Apr '21

29 Apr '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1184385 http://bugzilla.opensuse.org/show_bug.cgi?id=1184385#c1 Attila Pinter <adathor(a)opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |adathor(a)opensuse.org --- Comment #1 from Attila Pinter <adathor(a)opensuse.org> --- The same scenario is true for a "Container host" role as well. Firewalld should be part of the offline installer or need an option to add online repositories from YaST. Probably including the package to satisfy the requirements of the feature made available in the installer is an easier way to deal with the problem. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1184525] container-registry - # reg ls localhost - connect: connection refused
by bugzilla_noreply＠suse.com 26 Apr '21

26 Apr '21

https://bugzilla.suse.com/show_bug.cgi?id=1184525 Thorsten Kukuk <kukuk(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(colony.three@prot | |onmail.ch) | -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1185290] [Build 20210425] Invalid 'driver' setting in MicroOS image
by bugzilla_noreply＠suse.com 26 Apr '21

26 Apr '21

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

1 0

[Bug 1185290] New: [Build 20210425] Invalid 'driver' setting in MicroOS image
by bugzilla_noreply＠suse.com 26 Apr '21

26 Apr '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1185290 Bug ID: 1185290 Summary: [Build 20210425] Invalid 'driver' setting in MicroOS image Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/1714777/modules/tool box/steps/52 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kubic Assignee: kubic-bugs(a)opensuse.org Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: openQA Blocker: Yes ## Observation openQA test in scenario microos-Tumbleweed-MicroOS-Image-ContainerHost-x86_64-container-host-old2microosnext@64bit fails in [toolbox](https://openqa.opensuse.org/tests/1714777/modules/toolbox/steps/52) ## Test suite description Boot from existing, static MicroOS ContainerHost image and transactional-update dup to snapshot under test. ## Reproducible Fails since (at least) Build [20210423](https://openqa.opensuse.org/tests/1711104) ## Expected result Last good: [20210422](https://openqa.opensuse.org/tests/1710114) (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 the assignee for the bug.

1 1

Your Bugzilla bug list needs attention.
by bugzilla_noreply＠suse.com 25 Apr '21

25 Apr '21

[This e-mail has been automatically generated.] You have one or more bugs assigned to you in the Bugzilla bug tracking system (http://bugzilla.suse.com/) that require attention. All of these bugs are in either the CONFIRMED, NEW, or REOPENED state, and have not been touched in 7 days or more. You need to take a look at them, and decide on an initial action. Generally, this means one of three things: (1) You decide this bug is really quick to deal with (like, it's INVALID), and so you get rid of it immediately. (2) You decide the bug doesn't belong to you, and you reassign it to someone else. (Hint: if you don't know who to reassign it to, make sure that the Component field seems reasonable, and then use the "Reset Assignee to default" option.) (3) You decide the bug belongs to you, but you can't solve it this moment. Ignore this email until you are actively working on this bug, when you should set the status to IN_PROGRESS. To get a list of all affected bugs, you can use this URL (bookmark it if you like!): http://bugzilla.suse.com/buglist.cgi?bug_status=CONFIRMED&bug_status=NEW&bu… Or, you can use the general query page, at http://bugzilla.suse.com/query.cgi Appended below are the individual URLs to get to all of your affected bugs that haven't been touched for 7 days or more. You will get this message once a week until you've dealt with these bugs! security enhancement: no setuid -> http://bugzilla.suse.com/show_bug.cgi?id=1171174 live-add-yast-repos: uses openSUSE-release -> http://bugzilla.suse.com/show_bug.cgi?id=1172100 MicroOS Desktop: Wired network requires root password -> http://bugzilla.suse.com/show_bug.cgi?id=1172656 transactional-update: warn about reboot etc. -> http://bugzilla.suse.com/show_bug.cgi?id=1173261 transactional-update: Notification on failing update -> http://bugzilla.suse.com/show_bug.cgi?id=1176882 cockpit-ws image is unusable -> http://bugzilla.suse.com/show_bug.cgi?id=1177487 [Build 51.1_15.3][MicroOS] Unknown group 'render' in 50-udev-default.rules -> http://bugzilla.suse.com/show_bug.cgi?id=1179453 [Build 20210128] openQA test fails in journal_check -> http://bugzilla.suse.com/show_bug.cgi?id=1181547 KDE: Flatpack Chromium not starting via x-scheme-handler/https -> http://bugzilla.suse.com/show_bug.cgi?id=1182199 [Staging J] YaST is not installing microos_base_zypper pattern for container host role, causing OpenQA test failures -> http://bugzilla.suse.com/show_bug.cgi?id=1183231 transactional server role has very inconsistent package selection (TW, SLE, Leap) -> http://bugzilla.suse.com/show_bug.cgi?id=1183582 MicroOS needs to no longer ship AppArmor -> http://bugzilla.suse.com/show_bug.cgi?id=1183894 MicroOS Desktop with GNOME is now in Beta -> http://bugzilla.suse.com/show_bug.cgi?id=1184037 firewalld missing in installer/installation image for MicroOS Desktop -> http://bugzilla.suse.com/show_bug.cgi?id=1184385 Opening polari flatpak crashes packagekitd and makes gnome go back to login screen -> http://bugzilla.suse.com/show_bug.cgi?id=1184411

1 0

Your Bugzilla bug list needs attention.
by bugzilla_noreply＠suse.com 18 Apr '21

18 Apr '21

[This e-mail has been automatically generated.] You have one or more bugs assigned to you in the Bugzilla bug tracking system (http://bugzilla.suse.com/) that require attention. All of these bugs are in either the CONFIRMED, NEW, or REOPENED state, and have not been touched in 7 days or more. You need to take a look at them, and decide on an initial action. Generally, this means one of three things: (1) You decide this bug is really quick to deal with (like, it's INVALID), and so you get rid of it immediately. (2) You decide the bug doesn't belong to you, and you reassign it to someone else. (Hint: if you don't know who to reassign it to, make sure that the Component field seems reasonable, and then use the "Reset Assignee to default" option.) (3) You decide the bug belongs to you, but you can't solve it this moment. Ignore this email until you are actively working on this bug, when you should set the status to IN_PROGRESS. To get a list of all affected bugs, you can use this URL (bookmark it if you like!): http://bugzilla.suse.com/buglist.cgi?bug_status=CONFIRMED&bug_status=NEW&bu… Or, you can use the general query page, at http://bugzilla.suse.com/query.cgi Appended below are the individual URLs to get to all of your affected bugs that haven't been touched for 7 days or more. You will get this message once a week until you've dealt with these bugs! security enhancement: no setuid -> http://bugzilla.suse.com/show_bug.cgi?id=1171174 live-add-yast-repos: uses openSUSE-release -> http://bugzilla.suse.com/show_bug.cgi?id=1172100 MicroOS Desktop: Wired network requires root password -> http://bugzilla.suse.com/show_bug.cgi?id=1172656 transactional-update: warn about reboot etc. -> http://bugzilla.suse.com/show_bug.cgi?id=1173261 transactional-update: Notification on failing update -> http://bugzilla.suse.com/show_bug.cgi?id=1176882 cockpit-ws image is unusable -> http://bugzilla.suse.com/show_bug.cgi?id=1177487 [Build 51.1_15.3][MicroOS] Unknown group 'render' in 50-udev-default.rules -> http://bugzilla.suse.com/show_bug.cgi?id=1179453 [Build 20210128] openQA test fails in journal_check -> http://bugzilla.suse.com/show_bug.cgi?id=1181547 KDE: Flatpack Chromium not starting via x-scheme-handler/https -> http://bugzilla.suse.com/show_bug.cgi?id=1182199 [Staging J] YaST is not installing microos_base_zypper pattern for container host role, causing OpenQA test failures -> http://bugzilla.suse.com/show_bug.cgi?id=1183231 transactional server role has very inconsistent package selection (TW, SLE, Leap) -> http://bugzilla.suse.com/show_bug.cgi?id=1183582 MicroOS needs to no longer ship AppArmor -> http://bugzilla.suse.com/show_bug.cgi?id=1183894 MicroOS Desktop with GNOME is now in Beta -> http://bugzilla.suse.com/show_bug.cgi?id=1184037 firewalld missing in installer/installation image for MicroOS Desktop -> http://bugzilla.suse.com/show_bug.cgi?id=1184385 Opening polari flatpak crashes packagekitd and makes gnome go back to login screen -> http://bugzilla.suse.com/show_bug.cgi?id=1184411

1 0

[Bug 1184753] salt-minion conflicts with busybox-hostname
by bugzilla_noreply＠suse.com 14 Apr '21

14 Apr '21

https://bugzilla.suse.com/show_bug.cgi?id=1184753 https://bugzilla.suse.com/show_bug.cgi?id=1184753#c1 Thorsten Kukuk <kukuk(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kukuk(a)suse.com Component|MicroOS |Salt Assignee|kubic-bugs(a)opensuse.org |salt-maintainers(a)suse.de --- Comment #1 from Thorsten Kukuk <kukuk(a)suse.com> --- This sounds more like broken dependencies of python38-psutil, which requires net-tools... -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1184753] New: salt-minion conflicts with busybox-hostname
by bugzilla_noreply＠suse.com 14 Apr '21

14 Apr '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1184753 Bug ID: 1184753 Summary: salt-minion conflicts with busybox-hostname 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: jgonzalez(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- openSUSE MicroOS installed from DVD (openSUSE-MicroOS-DVD-x86_64-Snapshot20210408-Media.iso), using the default System Role (MicroOS). After the installation is complete I try to install salt-minion, and it conflicts with busybox-hostname: > localhost:~ # transactional-update pkg install salt-minion > Checking for newer version. > transactional-update 3.3.0 started > Options: pkg install salt-minion > Separate /var detected. > 2021-04-14 15:05:16 tukit 3.3.0 started > 2021-04-14 15:05:16 Options: -c1 open > 2021-04-14 15:05:17 Using snapshot 1 as base for new snapshot 3. > 2021-04-14 15:05:17 No previous snapshot to sync with - skipping > ID: 3 > 2021-04-14 15:05:17 Transaction completed. > Calling zypper install > 2021-04-14 15:05:19 tukit 3.3.0 started > 2021-04-14 15:05:19 Options: callext 3 zypper -R {} install salt-minion > 2021-04-14 15:05:19 Executing `zypper -R /tmp/transactional-update-S4U6H4 install salt-minion`: > Loading repository data... > Reading installed packages... > Resolving package dependencies... > > Problem: salt-minion-3002.2-4.1.x86_64 requires salt = 3002.2-4.1, but this requirement cannot be provided > not installable providers: salt-3002.2-4.1.i586[repo-oss] > salt-3002.2-4.1.x86_64[repo-oss] > Solution 1: deinstallation of busybox-hostname-1.33.0-17.2.noarch > Solution 2: do not install salt-minion-3002.2-4.1.x86_64 > Solution 3: break salt-minion-3002.2-4.1.x86_64 by ignoring some of its dependencies > > Choose from above solutions by number or cancel [1/2/3/c/d/?] (c): If I pick solution 1, then busybox-hostname gets removed an apparently salt-minion works fine, but still I guess that having this conflict is not fine. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1184525] container-registry - # reg ls localhost - connect: connection refused
by bugzilla_noreply＠suse.com 14 Apr '21

14 Apr '21

https://bugzilla.suse.com/show_bug.cgi?id=1184525 https://bugzilla.suse.com/show_bug.cgi?id=1184525#c5 Thorsten Kukuk <kukuk(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #5 from Thorsten Kukuk <kukuk(a)suse.com> --- Ok, closing -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1184525] container-registry - # reg ls localhost - connect: connection refused
by bugzilla_noreply＠suse.com 12 Apr '21

12 Apr '21

https://bugzilla.suse.com/show_bug.cgi?id=1184525 https://bugzilla.suse.com/show_bug.cgi?id=1184525#c4 --- Comment #4 from Bill Southwell <colony.three(a)protonmail.ch> --- I deleted the config and insall of the registry, reinstalled, and now it works. Something went wrong with the config. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1184525] container-registry - # reg ls localhost - connect: connection refused
by bugzilla_noreply＠suse.com 12 Apr '21

12 Apr '21

https://bugzilla.suse.com/show_bug.cgi?id=1184525 https://bugzilla.suse.com/show_bug.cgi?id=1184525#c3 --- Comment #3 from Thorsten Kukuk <kukuk(a)suse.com> --- I installed a fresh plain MicroOS Container Host and followed the instructions from the blog: works out of the box without any problems. That 'nft' doesn't show anything doesn't surprise me, openSUSE uses "iptables". If you switched that somehow and it doesn't show anything, it's no wonder that it does not work: where are the podman rules? Either your container is not running (podman ps?), your you still have network problems. But the description itself is correct and still works. -- You are receiving this mail because: You are the assignee for the bug.

1 0

Your Bugzilla bug list needs attention.
by bugzilla_noreply＠suse.com 11 Apr '21

11 Apr '21

[This e-mail has been automatically generated.] You have one or more bugs assigned to you in the Bugzilla bug tracking system (http://bugzilla.suse.com/) that require attention. All of these bugs are in either the CONFIRMED, NEW, or REOPENED state, and have not been touched in 7 days or more. You need to take a look at them, and decide on an initial action. Generally, this means one of three things: (1) You decide this bug is really quick to deal with (like, it's INVALID), and so you get rid of it immediately. (2) You decide the bug doesn't belong to you, and you reassign it to someone else. (Hint: if you don't know who to reassign it to, make sure that the Component field seems reasonable, and then use the "Reset Assignee to default" option.) (3) You decide the bug belongs to you, but you can't solve it this moment. Ignore this email until you are actively working on this bug, when you should set the status to IN_PROGRESS. To get a list of all affected bugs, you can use this URL (bookmark it if you like!): http://bugzilla.suse.com/buglist.cgi?bug_status=CONFIRMED&bug_status=NEW&bu… Or, you can use the general query page, at http://bugzilla.suse.com/query.cgi Appended below are the individual URLs to get to all of your affected bugs that haven't been touched for 7 days or more. You will get this message once a week until you've dealt with these bugs! security enhancement: no setuid -> http://bugzilla.suse.com/show_bug.cgi?id=1171174 live-add-yast-repos: uses openSUSE-release -> http://bugzilla.suse.com/show_bug.cgi?id=1172100 MicroOS Desktop: Wired network requires root password -> http://bugzilla.suse.com/show_bug.cgi?id=1172656 transactional-update: warn about reboot etc. -> http://bugzilla.suse.com/show_bug.cgi?id=1173261 transactional-update: Notification on failing update -> http://bugzilla.suse.com/show_bug.cgi?id=1176882 cockpit-ws image is unusable -> http://bugzilla.suse.com/show_bug.cgi?id=1177487 [Build 51.1_15.3][MicroOS] Unknown group 'render' in 50-udev-default.rules -> http://bugzilla.suse.com/show_bug.cgi?id=1179453 [Build 20210128] openQA test fails in journal_check -> http://bugzilla.suse.com/show_bug.cgi?id=1181547 KDE: Flatpack Chromium not starting via x-scheme-handler/https -> http://bugzilla.suse.com/show_bug.cgi?id=1182199 [Staging J] YaST is not installing microos_base_zypper pattern for container host role, causing OpenQA test failures -> http://bugzilla.suse.com/show_bug.cgi?id=1183231 transactional server role has very inconsistent package selection (TW, SLE, Leap) -> http://bugzilla.suse.com/show_bug.cgi?id=1183582 MicroOS needs to no longer ship AppArmor -> http://bugzilla.suse.com/show_bug.cgi?id=1183894 MicroOS Desktop with GNOME is now in Beta -> http://bugzilla.suse.com/show_bug.cgi?id=1184037

1 0

[Bug 1184525] container-registry - # reg ls localhost - connect: connection refused
by bugzilla_noreply＠suse.com 10 Apr '21

10 Apr '21

https://bugzilla.suse.com/show_bug.cgi?id=1184525 https://bugzilla.suse.com/show_bug.cgi?id=1184525#c2 --- Comment #2 from Bill Southwell <colony.three(a)protonmail.ch> --- My Quantum account got destroyed somehow. Continuing: I have disabled my firewall, as shown above. # reg ls localhost INFO[0000] domain: localhost INFO[0000] server address: localhost Get "https://localhost/v2/": dial tcp 127.0.0.1:443: connect: connection refused # nft -s list ruleset # dmesg -c # systemctl restart container-registry # dmesg [Fri Apr 9 08:41:25 2021] cni-podman0: port 1(veth3f6a048d) entered disabled state [Fri Apr 9 08:41:25 2021] device veth3f6a048d left promiscuous mode [Fri Apr 9 08:41:25 2021] cni-podman0: port 1(veth3f6a048d) entered disabled state [Fri Apr 9 08:41:28 2021] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [Fri Apr 9 08:41:28 2021] cni-podman0: port 1(vetha8e962d9) entered blocking state [Fri Apr 9 08:41:28 2021] cni-podman0: port 1(vetha8e962d9) entered disabled state [Fri Apr 9 08:41:28 2021] device vetha8e962d9 entered promiscuous mode [Fri Apr 9 08:41:28 2021] cni-podman0: port 1(vetha8e962d9) entered blocking state [Fri Apr 9 08:41:28 2021] cni-podman0: port 1(vetha8e962d9) entered forwarding state # # nft -s list ruleset # # reg ls localhost INFO[0000] domain: localhost INFO[0000] server address: localhost Get "https://localhost/v2/": dial tcp 127.0.0.1:443: connect: connection refused # -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1184525] container-registry - # reg ls localhost - connect: connection refused
by bugzilla_noreply＠suse.com 09 Apr '21

09 Apr '21

https://bugzilla.suse.com/show_bug.cgi?id=1184525 https://bugzilla.suse.com/show_bug.cgi?id=1184525#c1 Thorsten Kukuk <kukuk(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |colony.three(a)protonmail.ch Flags| |needinfo?(colony.three@prot | |onmail.ch) --- Comment #1 from Thorsten Kukuk <kukuk(a)suse.com> --- So your firewall forbids traffic to/between the containers? In this case reg can of course not work if you forbid the communication. Disable your firewall, reload the podman network and try it again. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1184525] container-registry - # reg ls localhost - connect: connection refused
by bugzilla_noreply＠suse.com 09 Apr '21

09 Apr '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1184525 Klaus K�mpf <kkaempf(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kkaempf(a)suse.com Component|Containers |Kubic Assignee|containers-bugowner(a)suse.de |kubic-bugs(a)opensuse.org -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1184411] New: Opening polari flatpak crashes packagekitd and makes gnome go back to login screen
by bugzilla_noreply＠suse.com 06 Apr '21

06 Apr '21

https://bugzilla.suse.com/show_bug.cgi?id=1184411 Bug ID: 1184411 Summary: Opening polari flatpak crashes packagekitd and makes gnome go back to login screen 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: mpdesouza(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Version: cat /etc/os-release NAME="openSUSE MicroOS" # VERSION="20210329" ID="opensuse-microos" ID_LIKE="suse opensuse opensuse-tumbleweed" VERSION_ID="20210329" How to reproduce: * Install polari from flathub * Open polari * packagekitd crashes, gnome goes back to login screen Apr 06 11:47:46 linux.local PackageKit[21387]: daemon start Apr 06 11:47:52 linux.local packagekitd[21387]: Error resolving real path of cd:/?devices=/dev/disk/by-id/scsi-0QEMU_QEMU_DVD-ROM_QM00001: No such file or directory Apr 06 11:47:52 linux.local kernel: packagekitd[21387]: segfault at 0 ip 00007f85600fea5f sp 00007fff3508ca40 error 4 in libdnf.so.2[7f85600b2000+171000] Apr 06 11:47:52 linux.local kernel: Code: e8 c6 a0 fb ff 49 89 c6 48 39 c3 75 ce 66 0f 1f 44 00 00 48 8b b5 70 ff ff ff 48 8b bd 68 ff ff ff 31 c9 31 d2 e8 a1 59 fb ff <4c> 8b 20 48 89 85 48 ff ff ff 4d 85 e4 0f 84 4e 02 00 00 48 89 85 Easily reproducible. Let me know if you need more data. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1184385] New: firewalld missing in installer/installation image for MicroOS Desktop
by bugzilla_noreply＠suse.com 06 Apr '21

06 Apr '21

https://bugzilla.suse.com/show_bug.cgi?id=1184385 Bug ID: 1184385 Summary: firewalld missing in installer/installation image for MicroOS Desktop 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: martin.rohde(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- When trying to enable the firewall in the 'Security' section of the Yast installation settings, the following message appears in the 'Software' section: "These packages need to be selected to install: firewalld Please manually select the needed items to install." Searching within Yast during the installation doesn't produce any results. It looks like firewalld is not available as part of the current image available via https://get.opensuse.org/microos/ I think for desktop use cases firewalld should be enabled by default in the installer. -- You are receiving this mail because: You are the assignee for the bug.

1 0

Your Bugzilla bug list needs attention.
by bugzilla_noreply＠suse.com 04 Apr '21

04 Apr '21

[This e-mail has been automatically generated.] You have one or more bugs assigned to you in the Bugzilla bug tracking system (http://bugzilla.suse.com/) that require attention. All of these bugs are in either the CONFIRMED, NEW, or REOPENED state, and have not been touched in 7 days or more. You need to take a look at them, and decide on an initial action. Generally, this means one of three things: (1) You decide this bug is really quick to deal with (like, it's INVALID), and so you get rid of it immediately. (2) You decide the bug doesn't belong to you, and you reassign it to someone else. (Hint: if you don't know who to reassign it to, make sure that the Component field seems reasonable, and then use the "Reset Assignee to default" option.) (3) You decide the bug belongs to you, but you can't solve it this moment. Ignore this email until you are actively working on this bug, when you should set the status to IN_PROGRESS. To get a list of all affected bugs, you can use this URL (bookmark it if you like!): http://bugzilla.suse.com/buglist.cgi?bug_status=CONFIRMED&bug_status=NEW&bu… Or, you can use the general query page, at http://bugzilla.suse.com/query.cgi Appended below are the individual URLs to get to all of your affected bugs that haven't been touched for 7 days or more. You will get this message once a week until you've dealt with these bugs! security enhancement: no setuid -> http://bugzilla.suse.com/show_bug.cgi?id=1171174 live-add-yast-repos: uses openSUSE-release -> http://bugzilla.suse.com/show_bug.cgi?id=1172100 MicroOS Desktop: Wired network requires root password -> http://bugzilla.suse.com/show_bug.cgi?id=1172656 transactional-update: warn about reboot etc. -> http://bugzilla.suse.com/show_bug.cgi?id=1173261 transactional-update: Notification on failing update -> http://bugzilla.suse.com/show_bug.cgi?id=1176882 cockpit-ws image is unusable -> http://bugzilla.suse.com/show_bug.cgi?id=1177487 [Build 51.1_15.3][MicroOS] Unknown group 'render' in 50-udev-default.rules -> http://bugzilla.suse.com/show_bug.cgi?id=1179453 [Build 20210128] openQA test fails in journal_check -> http://bugzilla.suse.com/show_bug.cgi?id=1181547 KDE: Flatpack Chromium not starting via x-scheme-handler/https -> http://bugzilla.suse.com/show_bug.cgi?id=1182199 [Staging J] YaST is not installing microos_base_zypper pattern for container host role, causing OpenQA test failures -> http://bugzilla.suse.com/show_bug.cgi?id=1183231 transactional server role has very inconsistent package selection (TW, SLE, Leap) -> http://bugzilla.suse.com/show_bug.cgi?id=1183582 MicroOS needs to no longer ship AppArmor -> http://bugzilla.suse.com/show_bug.cgi?id=1183894 MicroOS Desktop with GNOME is now in Beta -> http://bugzilla.suse.com/show_bug.cgi?id=1184037

1 0