January 2022 - openSUSE Kubic Bugs - openSUSE Mailing Lists

[Bug 1194458] New: microos out of space chain reaction
by bugzilla_noreply＠suse.com 13 Jan '22

13 Jan '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1194458 Bug ID: 1194458 Summary: microos out of space chain reaction 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: --- On my rpi with MicroOS an erroneously created subvolume @/.snapshots/46/snapshot/var/lib/machines lead to snapper-cleanup not removing snapshots. snapper-cleanup.service as activated from timer failed without consequences. That in turn filled up the disk over time. At some point transactional-update started to fail: 2022-01-05 02:03:24 Application returned with exit status 8. 2022-01-05 02:03 ERROR: zypper --no-cd dup on /.snapshots/92/snapshot failed with exit code 8! It did keep the downloaded rpms in the cache, so available disk space got smaller. Two days later journald couldn't write logs anymore: Jan 07 00:39:38 heizung systemd-journald[27385]: Journal started Jan 07 00:39:44 heizung systemd-journald[27385]: Runtime Journal (/run/log/journal/f8c8ba660edd4757982d57b4a1f8ba64) is 18.6M, max 18.6M, 0B free. Jan 07 00:39:51 heizung systemd-journald[27385]: Missed 31 kernel messages Jan 07 00:39:51 heizung systemd-journald[27027]: File /var/log/journal/f8c8ba660edd4757982d57b4a1f8ba64/system.journal corrupted or uncleanly shut down, renaming and replacing. At Jan 10th I noticed something was wrong and tried to log in via ssh which wasn't possible anymore: debug1: pledge: filesystem full �� Had to take the SD card to manually free some space and make the system boot again. Independent of the individual failures in this chain reaction the system could have communicated it's in trouble early somehow. Esp the snapper-cleanup fail was going on for almost a year where I logged in via ssh and didn't notice. In the event of almost full disk the system made the situation worse by keeping cached rpms. Journald didn't take any emergency action in the disk full situation, eg to free space. The journal was 1.7G on a 15G disk with 50000 tiny .journal~ files in /var/log/journal/$UUID. Last but not least sshd didn't allow login as root anymore. -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1188939] SELinux prevents podman from being run as a systemd service and from being updated
by bugzilla_noreply＠suse.com 12 Jan '22

12 Jan '22

https://bugzilla.suse.com/show_bug.cgi?id=1188939 https://bugzilla.suse.com/show_bug.cgi?id=1188939#c1 Miroslav Grepl <miroslav.grepl(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |miroslav.grepl(a)suse.com --- Comment #1 from Miroslav Grepl <miroslav.grepl(a)suse.com> --- Hello. can you still reproduce this issue? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1186943] snapper cleanup: Deleting snapshot failed.
by bugzilla_noreply＠suse.com 11 Jan '22

11 Jan '22

https://bugzilla.suse.com/show_bug.cgi?id=1186943 https://bugzilla.suse.com/show_bug.cgi?id=1186943#c4 --- Comment #4 from Ludwig Nussel <lnussel(a)suse.com> --- The failing service is snapper-cleanup.service though. I'm not sure adding extra magic to t-u is the right place. Maybe snapper could just skip over snapshots that can't be deleted instead of exiting. It could of course still exit with failure in the end but try as best as it can. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1186943] snapper cleanup: Deleting snapshot failed.
by bugzilla_noreply＠suse.com 11 Jan '22

11 Jan '22

https://bugzilla.suse.com/show_bug.cgi?id=1186943 https://bugzilla.suse.com/show_bug.cgi?id=1186943#c3 --- Comment #3 from Ignaz Forster <iforster(a)suse.com> --- One option to get out of this may be to extend the "cleanup" command of transactional-update to check for invalid configurations such as these. In this case snapshot subvolumes could be deleted if they exist... -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1193706] pkcon reporting a (spurious?) read-only fs error
by bugzilla_noreply＠suse.com 10 Jan '22

10 Jan '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1193706 http://bugzilla.opensuse.org/show_bug.cgi?id=1193706#c4 Ignaz Forster <iforster(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(iforster(a)suse.com | |) | --- Comment #4 from Ignaz Forster <iforster(a)suse.com> --- Oh dear, I'm sorry, I completely forgot to reply to this ticket - thanks for the fix! -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1193706] pkcon reporting a (spurious?) read-only fs error
by bugzilla_noreply＠suse.com 10 Jan '22

10 Jan '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1193706 http://bugzilla.opensuse.org/show_bug.cgi?id=1193706#c3 --- Comment #3 from OBSbugzilla Bot <bwiedemann+obsbugzillabot(a)suse.com> --- This is an autogenerated message for OBS integration: This bug (1193706) was mentioned in https://build.opensuse.org/request/show/945339 Factory / dnf https://build.opensuse.org/request/show/945344 Backports:SLE-15-SP4 / dnf -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1193706] pkcon reporting a (spurious?) read-only fs error
by bugzilla_noreply＠suse.com 10 Jan '22

10 Jan '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1193706 http://bugzilla.opensuse.org/show_bug.cgi?id=1193706#c2 --- Comment #2 from Neal Gompa <ngompa13(a)gmail.com> --- I've added /etc/dnf/modules.d to the dnf-data subpackage, which should fix this useless error: https://build.opensuse.org/request/show/945338 -- You are receiving this mail because: You are the assignee for the bug.

1 0