- openSUSE Kubic Bugs

[Bug 1216997] patterns-microos-cockpit/microos_cockpit name is not aligned to the same in SLE products
by bugzilla_noreply＠suse.com 16 Nov '23

16 Nov '23

https://bugzilla.suse.com/show_bug.cgi?id=1216997 https://bugzilla.suse.com/show_bug.cgi?id=1216997#c1 Thorsten Kukuk <kukuk(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |INVALID Status|NEW |RESOLVED CC| |jsrain(a)suse.com --- Comment #1 from Thorsten Kukuk <kukuk(a)suse.com> --- Patterns are defined via provides. RPM will handle "-" as separator for name and version number in provides. So using "-" in patterns names can have unwanted side effects. For this reason, we had to change all patterns in Factory from "-" to "_" some time ago. We will not revert this. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1206121] Slow system shutdown due to the failure of stopping a distrobox container
by bugzilla_noreply＠suse.com 13 Nov '23

13 Nov '23

https://bugzilla.suse.com/show_bug.cgi?id=1206121 https://bugzilla.suse.com/show_bug.cgi?id=1206121#c2 Fred Fu <moonsolo(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #2 from Fred Fu <moonsolo(a)gmail.com> --- The issue has been solved -- You are receiving this mail because: You are the assignee for the bug.

1 0

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

13 Nov '23

https://bugzilla.suse.com/show_bug.cgi?id=1216090 https://bugzilla.suse.com/show_bug.cgi?id=1216090#c3 --- Comment #3 from Johannes Segitz <jsegitz(a)suse.com> --- we please need the information Cathy requested to work on this. Thanks -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1216997] New: patterns-microos-cockpit/microos_cockpit name is not aligned to the same in SLE products
by bugzilla_noreply＠suse.com 09 Nov '23

09 Nov '23

https://bugzilla.suse.com/show_bug.cgi?id=1216997 Bug ID: 1216997 Summary: patterns-microos-cockpit/microos_cockpit name is not aligned to the same in SLE products 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: michele.pagot(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- They do not necessary needs to be the same as they belong to different products. But in this case the difference is minimal: - Name in SLE is microos-cockpit - Name in openSUSE is with underscore microos_cockpit Here a reference to the name in SLE https://documentation.suse.com/sle-micro/5.1/html/SLE-Micro-all/article-adm… Issue is also reported by some user https://github.com/cockpit-project/cockpit-project.github.io/issues/666 -- You are receiving this mail because: You are the assignee for the bug.

1 0

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

02 Nov '23

https://bugzilla.suse.com/show_bug.cgi?id=1216090 Hu <cathy.hu(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(olivpass(a)web.de) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[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