Project

General

Profile

action #87749

[VMWare] journactl missing boot ID

Added by mloviska 8 months ago. Updated 7 months ago.

Status:
Resolved
Priority:
High
Assignee:
Category:
Bugs in existing tests
Target version:
-
Start date:
2021-01-14
Due date:
% Done:

0%

Estimated time:
Difficulty:
Tags:

Description

Observation

openQA test in scenario sle-15-SP3-JeOS-for-VMware-x86_64-jeos-extratest@svirt-vmware65 fails in
journalctl

Test suite description

Isolated test case seems to work as expected, however jeos-extratest@svirt-vmware65 exposed an issue either in the test code or an integration issue within test suite.

Reproducible

Fails since (at least) Build 20.139

Expected result

Last good: (unknown) (or more recent)

Further details

Always latest result in this scenario: latest

History

#3 Updated by mloviska 8 months ago

1c208:~ # systemd-detect-virt 
vmware
1c208:~ # journalctl --list-boots
-1 1bce4b19b8074f6f9288805a4e036b7d Thu 2021-01-21 12:49:38 UTC—Thu 2021-01-21 13:20:38 UTC
 0 018f5e8a1be34a2e946bcb67645f1fd6 Thu 2021-01-21 13:20:57 UTC—Thu 2021-01-21 12:58:16 UTC
1c208:~ # journalctl --boot=-1                                                                  
-- Logs begin at Thu 2021-01-21 12:49:38 UTC, end at Thu 2021-01-21 13:21:08 UTC. --
Jan 21 12:49:38 localhost kernel: Linux version 5.3.18-43-default (geeko@buildhost) (gcc version 7.5.0 (SUSE Linux)) #1 SMP Wed Jan 13 10:25:28 UTC 2021 (404436f)
Jan 21 12:49:38 localhost kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.3.18-43-default root=UUID=0e84c302-0fb2-4e29-a694-83ea442a0451 rw plymouth.enable=0 console=ttyS0,115200 console=tt>
Jan 21 12:49:38 localhost kernel: Disabled fast string operations
Jan 21 12:49:38 localhost kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
Jan 21 12:49:38 localhost kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
Jan 21 12:49:38 localhost kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
Jan 21 12:49:38 localhost kernel: x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
Jan 21 12:49:38 localhost kernel: x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'standard' format.
Jan 21 12:49:38 localhost kernel: BIOS-provided physical RAM map:
Jan 21 12:49:38 localhost kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009f7ff] usable 

Seems like a test issue instead of product issue...not sure why though

#4 Updated by okurz 7 months ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: jeos-extratest@svirt-xen-hvm
https://openqa.suse.de/tests/5452136

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released"
  3. The label in the openQA scenario is removed

#5 Updated by mloviska 7 months ago

  • Status changed from In Progress to Resolved

#7 Updated by mloviska 7 months ago

░░ The job identifier is 10467.
Feb 24 19:08:12 localhost systemd-journald[16263]: Time spent on flushing to /var/log/journal/6c132f8931d648eeae0f0be621b57fc5 is 40.036ms for 2472 entries.
Feb 24 19:08:12 localhost systemd-journald[16263]: System Journal (/var/log/journal/6c132f8931d648eeae0f0be621b57fc5) is 8.0M, max 2.3G, 2.3G free.
░░ Subject: Disk space used by the journal
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ System Journal (/var/log/journal/6c132f8931d648eeae0f0be621b57fc5) is currently using 8.0M.
░░ Maximum allowed usage is set to 2.3G.
░░ Leaving at least 1.1G free (of currently available 22.3G of disk space).
░░ Enforced usage limit is thus 2.3G, of which 2.3G are still available.
░░ 
░░ The limits controlling how much disk space is used by the journal may
░░ be configured with SystemMaxUse=, SystemKeepFree=, SystemMaxFileSize=,
░░ RuntimeMaxUse=, RuntimeKeepFree=, RuntimeMaxFileSize= settings in
░░ /etc/systemd/journald.conf. See journald.conf(5) for details.
Feb 24 19:08:12 localhost batman[16265]: CALL THE BATMAN NOW!1!! AARRGGH!!
Feb 24 19:08:12 localhost batman[16266]: We NEED to call the batman NOW
Feb 24 19:08:12 localhost systemd[1]: Finished Flush Journal to Persistent Storage.
░░ Subject: A start job for unit systemd-journal-flush.service has finished successfully
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit systemd-journal-flush.service has finished successfully.
░░ 
░░ The job identifier is 10467.
Feb 24 19:08:12 localhost batman[16267]: We need to call batman

#8 Updated by mloviska 7 months ago

# test -S /run/systemd/journal/syslog; echo fwt9U-$?-
fwt9U-0-
# curl --form upload=@/var/log/messages --form upname=journalctl-messages http://10.0.2.2:20073/qcTvZOGFe0v1TWUk/uploadlog/messages; echo nEDAi-$?-
OK: journalctl-messages
nEDAi-0-
# systemctl --no-pager restart systemd-journald; echo uAvSy-$?-
uAvSy-0-
# systemd-cat --priority=emerg --identifier=batman echo 'CALL THE BATMAN NOW!1!! AARRGGH!!'; echo 6q3Cv-$?-
6q3Cv-0-
# systemd-cat --priority=err --identifier=batman echo 'We NEED to call the batman NOW'; echo DOXWv-$?-
DOXWv-0-
# systemd-cat --priority=info --identifier=batman echo 'We need to call batman'; echo l2nZh-$?-
l2nZh-0-
# journalctl --boot=b37a5d0d095d478396477b1b4a39e94e --identifier=batman --priority=emerg --output=short | grep 'CALL THE BATMAN NOW!1!! AARRGGH!!'; echo BrVL1-$?-
BrVL1-1-
# 

Broadcast message from systemd-journald@localhost (Wed 2021-02-24 19:08:12 UTC):



batman[16265]: CALL THE BATMAN NOW!1!! AARRGGH!!



journalctl -x > /var/tmp/journalctl.txt; echo VBL3K-$?-
VBL3K-0-

Maybe the test is too fast for journald ?!

Also available in: Atom PDF