[Bug 1228378] New: [Build 20240726] openQA test fails in aa_notify. File Not Found: /var/log/wtmp
https://bugzilla.suse.com/show_bug.cgi?id=1228378 Bug ID: 1228378 Summary: [Build 20240726] openQA test fails in aa_notify. File Not Found: /var/log/wtmp Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/4361427/modules/aa_n otify/steps/17 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: AppArmor Assignee: suse-beta@cboltz.de Reporter: nada-infinita@posteo.net QA Contact: qa-bugs@suse.de Target Milestone: --- Found By: openQA Blocker: Yes Created attachment 876301 --> https://bugzilla.suse.com/attachment.cgi?id=876301&action=edit Error mssg image ## Observation
# Test died: script failed with : K5_x4 SCRIPT_FINISHEDK5_x4-1- at /usr/lib/os-autoinst/distribution.pm line 303.
openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-apparmor@64bit fails in [aa_notify](https://openqa.opensuse.org/tests/4361427/modules/aa_notify/steps/17) ## Test suite description Maintainer: QE Security; test AppArmor tool with an existing disk image. ## Reproducible Fails since (at least) Build [20231102](https://openqa.opensuse.org/tests/3699475) ## Expected result Last good: [20231020](https://openqa.opensuse.org/tests/3662635) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=opensuse&flavor=DVD&machine=64bit&test=apparmor&version=Tumbleweed) -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1228378 https://bugzilla.suse.com/show_bug.cgi?id=1228378#c1 Christian Boltz <suse-beta@cboltz.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Christian Boltz <suse-beta@cboltz.de> --- Known bug, see bug 1216660 Unfortunately lastlog2 doesn't have a way to get machine-readable output (for example json), so I'll have to implement parsing for the output that is meant for humans, and hope that it won't change... Actually I just implemented that, see https://gitlab.com/apparmor/apparmor/-/merge_requests/1282 - and will add it to the openSUSE package if it survives upstream review ;-) *** This bug has been marked as a duplicate of bug 1216660 *** -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1228378 https://bugzilla.suse.com/show_bug.cgi?id=1228378#c3 --- Comment #3 from Christian Boltz <suse-beta@cboltz.de> --- (In reply to Thorsten Kukuk from comment #2)
You mixed up lastlog2 with wtmpdb. Lastlog2 is the successor of lastlog, while wtmpdb is the replacement for /var/log/wtmp
Right (and thanks for pointing it out!), but since I'm only interested in the last login, lastlog2 loooked like a better fit. In the meantime, I found out that parsing the output of lastlog2 is harder than I thought - despite including the timezone ("+0200"), the result (converted to unixtime) depends on $TZ :-( That makes reading directly from /var/lib/lastlog/lastlog2.db looking more interesting and easy. The obvious disadvantage is that it would mean to use the back door instead of the official (but harder to use) front door tools. Is the database layout of /var/lib/lastlog/lastlog2.db expected to be quite stable, or is it a terrible idea to directly access it? -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠suse.com