Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

edge-minimal-9.5 and edge-minimal-arm-9.5 journald don't have persistent logging #7819

Open
mcattamoredhat opened this issue Jun 10, 2024 · 0 comments

Comments

@mcattamoredhat
Copy link
Collaborator

It has been seen that edge-minimal-9.5 and edge-minimal-arm-9.5 journald hasn't persistent logging.

RHEL 9.5 compose RHEL-9.5.0-20240608.41
Date: 2024-06-09
Packages:
osbuild-119-1.el9.noarch.rpm
osbuild-composer-109-1.el9.x86_64.rpm
weldr-client-35.12-2.el9.x86_64.rpm

List boots output example:

[admin@vm-2 ~]$ journalctl --list-boots -q
0 1ebff91eabf8469ea5d8100528cef4e9 Mon 2024-06-10 05:55:26 EDT Mon 2024-06-10 06:09:16 EDT
[admin@vm-2 ~]$ journalctl --boot=-1
Data from the specified boot (-1) is not available: No such boot ID in journal

Failed playbook task example output:

TASK [list boots] **************************************************************
changed: [192.168.100.51] => changed=true 
  cmd: journalctl --list-boots -q
  delta: '0:00:00.011104'
  end: '2024-06-10 03:40:05.951215'
  msg: ''
  rc: 0
  start: '2024-06-10 03:40:05.940111'
  stderr: ''
  stderr_lines: <omitted>
  stdout: 0 a302cddad6fa47aab9be6dde529894e4 Mon 2024-06-10 03:39:11 EDT Mon 2024-06-10 03:40:05 EDT
  stdout_lines: <omitted>

TASK [assert] ******************************************************************
fatal: [192.168.100.51]: FAILED! => changed=false 
  assertion: result_list_boots.stdout_lines | length > 1
  evaluated_to: false
  msg: journald hasn't persistent logging
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant