-
Notifications
You must be signed in to change notification settings - Fork 401
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
Do not use a machine-id value of uninitialized #2267
Comments
See #1873 (comment) |
This issue is about |
From your POV would it be appropriate to make |
I think the reproducer would have been clearer with In [dracut.sh[(https://github.com/dracutdevs/dracut/blob/master/dracut.sh#L1086#L1094),
Even better would be a regex check that's it's actually an UUID, the value |
As far as I can tell, the value of |
Thanks for your further explanation, now the issue is clear. |
Handle the case where the user tries to generate the initrd after explicitly resetting the /etc/machine-id file. Fixes issue dracutdevs#2267
Handle the case where the user tries to generate the initrd after explicitly resetting the /etc/machine-id file. Fixes issue #2267
Handle the case where the user tries to generate the initrd after explicitly resetting the /etc/machine-id file. Fixes issue dracutdevs#2267 (cherry picked from commit 97fe097)
Handle the case where the user tries to generate the initrd after explicitly resetting the /etc/machine-id file. Fixes issue dracutdevs#2267
Describe the bug
systemd supports writing
uninitialized
to/etc/machine-id
, which can be used forsystemd-firstboot
instead of removing/etc/machine-id
. Dracut does not check the contents of this file to populateMACHINE_ID
, so the valueunitialized
is usedDistribution used
Debian bookworm (12)
Dracut version
059
Init system
systemd
To Reproduce
Expected behavior
Dracut behaves as if there was no
machine-id
set, i.e. settingMACHINE_ID="Default"
.Additional context
The text was updated successfully, but these errors were encountered: