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

Journal is recreated with a different machine ID after reboot on VMWare #1536

Closed
arnaldo2792 opened this issue Apr 29, 2021 · 0 comments · Fixed by #1537
Closed

Journal is recreated with a different machine ID after reboot on VMWare #1536

arnaldo2792 opened this issue Apr 29, 2021 · 0 comments · Fixed by #1537
Labels
type/bug Something isn't working

Comments

@arnaldo2792
Copy link
Contributor

Image I'm using:
Bottlerocket vmware-dev

What I expected to happen:
Systemd shouldn't use the random machine id generator for the journal file

What actually happened:
Systemd is using the random machine id generator for the journal file

How to reproduce the problem:

  • Launch a vmware-dev host
  • Reboot
  • Run journalctl --list-boots from sheltie, and only the last boot's logs will appear
@arnaldo2792 arnaldo2792 linked a pull request Apr 29, 2021 that will close this issue
@jhaynes jhaynes added priority/p0 status/needs-triage Pending triage or re-evaluation type/bug Something isn't working labels Apr 29, 2021
@bcressey bcressey removed the status/needs-triage Pending triage or re-evaluation label Nov 11, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants