October 2023 - openSUSE Kubic Bugs - openSUSE Mailing Lists

[Bug 1216090] MicroOS, selinux is preventing nfsv4 upcall request-key, nfsidmap
by bugzilla_noreply＠suse.com 31 Oct '23

31 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1216090 https://bugzilla.suse.com/show_bug.cgi?id=1216090#c2 --- Comment #2 from Hu <cathy.hu(a)suse.com> --- Hi, i just wanted to give quick update. I am still struggling to reproduce this issue. However, we have had some recent fixes in the same area, so it could be that yours could be resolved with one. I staged an update here: https://build.opensuse.org/package/show/security:SELinux/selinux-policy Please try to add the repository and update to the selinux-policy and selinux-policy-targeted to the latest version on there. (If you don't want to add the repository, please wait until the following request is accepted and released, then you can just do a regular update: https://build.opensuse.org/request/show/1121154 ) If after that the issue is still not resolved, could you please send me the following things: - SELinux policy version: zypper info selinux-policy - Output of: restorecon -Rvn / - The AVCs that came out of the failed test Thanks a lot! -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1216367] New: The "/.snapshot/grub-snapshot.cfg" file has disappeared weeks ago and I can't boot from a Btrfs snapshot in openSUSE MicroOS/Aeon
by bugzilla_noreply＠suse.com 19 Oct '23

19 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1216367 Bug ID: 1216367 Summary: The "/.snapshot/grub-snapshot.cfg" file has disappeared weeks ago and I can't boot from a Btrfs snapshot in openSUSE MicroOS/Aeon Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: MicroOS Assignee: kubic-bugs(a)opensuse.org Reporter: edurayasmedina(a)outlook.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/118.0 Build Identifier: Hi, sorry if I'm bothering people with this message, but I'm scared because I lost one of the most important features of a immutable operating system: temporary rollback. I changed my SSD one month ago and I didn't perceived it in the first time, but I see that the snapshot entries don't appear in the GRUB menu. After a little investigation, first I see that the "/.snapshot/grub-snapshot.cfg" is not there and after I see that it seems that some lines of the "/boot/grub2/grub.cfg" file are missing. If you take an ISO image (snapshot) from two weeks ago, you can see the problem, and I can reproduce the problem with the latest ISO image. I always enable the firewall and disable SSH because I use MicroOS/Aeon for basic desktop purposes with some containers that I use as a toy. I reported the bug here, but I'm starting to think that it was the wrong place. Sorry for the thing I do bad and my bad English. https://bugzilla.opensuse.org/show_bug.cgi?id=1216292 Reproducible: Always Steps to Reproduce: 1. Install a recent snapshot (ISO image) 2. Do a regular installation on an UEFI system (even on GNOME Boxes). 3. You can see that entries for snapshots in GRUB menu have disappeared. Actual Results: I can't see the snapshots entries in the GRUB menu if I install openSUSE MicroOS/Aeon from a recent ISO image. I have an old installation in a laptop with disk encryption and I can see the snapshots to do a temporary rollback. I would like the see this corrected for my current installation. I will upload the information I could collect with my limited knowledge. -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 1216148] server:monitoring/monitoring-plugins: check_load is broken ("Error opening")
by bugzilla_noreply＠suse.com 16 Oct '23

16 Oct '23

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

1 0

[Bug 1216148] monitoring-plugins, check_load is broken ("Error opening")
by bugzilla_noreply＠suse.com 13 Oct '23

13 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1216148 https://bugzilla.suse.com/show_bug.cgi?id=1216148#c1 --- Comment #1 from William Brown <william.brown(a)suse.com> --- Affects Tumbleweed as well. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1216148] New: monitoring-plugins, check_load is broken ("Error opening")
by bugzilla_noreply＠suse.com 11 Oct '23

11 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1216148 Bug ID: 1216148 Summary: monitoring-plugins, check_load is broken ("Error opening") Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All 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 Target Milestone: --- Found By: --- Blocker: --- Created attachment 870104 --> https://bugzilla.suse.com/attachment.cgi?id=870104&action=edit Packages updated on 2023-10-11 Until the updated that got applied on openSUSE MicroOS last night, `/usr/lib/nagios/plugins/check_load -r -w 15,10,05 -c 30,25,20` worked fine. But since that update: microos:/var/log/zypp # /usr/lib/nagios/plugins/check_load -r -w 15,10,05 -c 30,25,20 CRITICAL - You need more args!!! Error opening I am not sure where the problem is, I see `monitoring-plugins-load` got updated, but the last changelog entry is from 2022, so I'd assume this was the result of some kind of mass rebuild (as the update as big, see the attached log with all the packages that got installed/updated). Last change on the package happened 1 year ago, according to https://build.opensuse.org/package/show/openSUSE:Factory/monitoring-plugins Seems Fedora had a bug that caused the same output years ago: https://bugzilla.redhat.com/show_bug.cgi?id=1470823, but it seems it got fixed by bumping their package to a 2018 commit based on 2.2.1 (https://src.fedoraproject.org/rpms/nagios-plugins/c/97402353898e984baebc50a…) so I'd say this is maybe not related. I reviewed apparmor changelogs, but could not see anything relevant either. Checking check_load's code, I'd say this is the line causing this: https://github.com/nagios-plugins/nagios-plugins/blob/master/plugins/check_… But the fact that CRITICAL error about args is showing confuses me. Checking https://github.com/nagios-plugins/nagios-plugins/blob/bade01b453b012af8c712…, I see `PATH_TO_UPTIME` is... well, basically seems to be the path to the `uptime` binary, that I can find and it works: microos:/var/log/zypp # which uptime /usr/bin/uptime microos:/var/log/zypp # uptime 17:31:47 up 13:01, 2 users, load average: 0.04, 0.01, 0.00 And given I am executing check_load as root and uptime has rights 755... I don't think this is a problem with the permissions. Can't see anything on any logs. I am out of ideas, so happy to debug a bit more if someone can provide a hint :-) -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1215709] segfault in libglib/libgio/libgobject 2.0.so.0.7800.0 since MicroOS-20230921
by bugzilla_noreply＠suse.com 10 Oct '23

10 Oct '23

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

1 0

[Bug 1215709] New: segfault in libglib/libgio/libgobject 2.0.so.0.7800.0 since MicroOS-20230921
by bugzilla_noreply＠suse.com 10 Oct '23

10 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1215709 Bug ID: 1215709 Summary: segfault in libglib/libgio/libgobject 2.0.so.0.7800.0 since MicroOS-20230921 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: VMWare OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: MicroOS Assignee: kubic-bugs(a)opensuse.org Reporter: dirk.datzert(a)gmx.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 869748 --> https://bugzilla.suse.com/attachment.cgi?id=869748&action=edit Hardcopy of the segfault messages After Upgrading to MicroOS-20230921 I see such segfaults pasted in the hardcopy on serveral VM Machines. I can revert to a snapshot from 20230918 and disable transactional-update.timer. Has this segfault seen somewhere else ? I'm running different k3s-version-branches on top of MicroOS and reverted also this to an older release. -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 1215903] MicroOS: current openstack image not allowing ssh keys to be added on digitalocean
by bugzilla_noreply＠suse.com 06 Oct '23

06 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1215903 https://bugzilla.suse.com/show_bug.cgi?id=1215903#c4 --- Comment #4 from Johannes Hölzel <freelancing(a)hoelzel.it> --- so root is locked and the update seems to uninstall container-selinux and consecutively rke2-selinux. I added both manually into my toolchain and now im up and running again. So to sum up the workaround is: - deploy deploy user with cloud-init - install selinux packages separatetly I guess pulling container selinux is fair when using the "Base System" image. Also i have seen that there has been a new iso provided on the 4th so i will check that now too. If anything this shows that we need a dedicated changelog for MicroOS and need to stop treating it as a component of tumbleweed. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1215903] MicroOS: current openstack image not allowing ssh keys to be added on digitalocean
by bugzilla_noreply＠suse.com 06 Oct '23

06 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1215903 https://bugzilla.suse.com/show_bug.cgi?id=1215903#c3 --- Comment #3 from Johannes Hölzel <freelancing(a)hoelzel.it> --- I think there is even more to it. I have currently adapted all my systems to use cloud-init but i can not even get rke2 to work at all. I checked the audit logs for selinux denies but there were none. Something has seriously crippled root and currently there is no way to run rke2 rootless... my current workaround is to deploy a deploy user with cloud-init and the old version then updated right with dup after. ``` users: - name: ${var.deploy_user} sudo: ALL=(ALL) NOPASSWD:ALL ssh_authorized_keys: - ${var.SSH_pub_key} ``` -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1215903] MicroOS: current openstack image not allowing ssh keys to be added on digitalocean
by bugzilla_noreply＠suse.com 06 Oct '23

06 Oct '23

https://bugzilla.suse.com/show_bug.cgi?id=1215903 https://bugzilla.suse.com/show_bug.cgi?id=1215903#c2 Klaas Kienemann <k.kienemann(a)theco.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |k.kienemann(a)theco.de --- Comment #2 from Klaas Kienemann <k.kienemann(a)theco.de> --- Same here - I've rolled back to MicroOS 20230927 and deactivated automatic transactional updates: systemctl --now disable transactional-update.timer sshd log output: "User root not allowed because account is locked" I suspect it is related to the libssh-config update in MicroOS 20230929. AFAIK cloud-init writes custom ssh configuration to /etc/ssh/sshd_config and libssh (libssh_server.config) does not parse this file any more. https://build.opensuse.org/request/show/1113627 I would like to enable automatic transactional updates back again. Are there any workarounds for this? -- You are receiving this mail because: You are the assignee for the bug.

1 0