From: Felix Moessbauer <felix.moessbauer@siemens.com>
To: isar-users@googlegroups.com
Cc: tobiasschmidl@siemens.com, henning.schild@siemens.com,
jan.kiszka@siemens.com, amikan@ilbers.de,
Felix Moessbauer <felix.moessbauer@siemens.com>
Subject: [PATCH v3] fix on-first-boot for systemd >= 247
Date: Tue, 2 Aug 2022 12:39:21 +0200 [thread overview]
Message-ID: <20220802103921.1481725-1-felix.moessbauer@siemens.com> (raw)
This patch fixes the bug that /etc/machine-id is never
generated when running from within an initrd with an ro rootfs.
In this case, the magic value "uninitialized" has to be used
instead of deleting the file.
For older systemd versions, we set it to the empty string
which is non-documented, but works as identified
in various tests on debian buster (systemd version 241).
Signed-off-by: Felix Moessbauer <felix.moessbauer@siemens.com>
---
meta/classes/image-postproc-extension.bbclass | 9 ++++++++-
1 file changed, 8 insertions(+), 1 deletion(-)
diff --git a/meta/classes/image-postproc-extension.bbclass b/meta/classes/image-postproc-extension.bbclass
index 0c412c0d..4a901cbf 100644
--- a/meta/classes/image-postproc-extension.bbclass
+++ b/meta/classes/image-postproc-extension.bbclass
@@ -56,8 +56,15 @@ image_postprocess_mark() {
ROOTFS_POSTPROCESS_COMMAND =+ "image_postprocess_machine_id"
image_postprocess_machine_id() {
# systemd(1) takes care of recreating the machine-id on first boot
+ # for systemd < v247, set to empty string, else set to uninitialized
+ # (required if initramfs with ro root is used)
+ SYSTEMD_VERSION=$( sudo chroot ${IMAGE_ROOTFS} dpkg-query --showformat='${source:Upstream-Version}' --show systemd || echo "0" )
+ MACHINE_ID="uninitialized"
+ if dpkg --compare-versions "$SYSTEMD_VERSION" "lt" "247"; then
+ MACHINE_ID=""
+ fi
+ echo "$MACHINE_ID" | sudo tee '${IMAGE_ROOTFS}/etc/machine-id'
sudo rm -f '${IMAGE_ROOTFS}/var/lib/dbus/machine-id'
- sudo rm -f '${IMAGE_ROOTFS}/etc/machine-id'
}
ROOTFS_POSTPROCESS_COMMAND =+ "image_postprocess_sshd_key_regen"
--
2.30.2
next reply other threads:[~2022-08-02 10:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-02 10:39 Felix Moessbauer [this message]
2022-08-09 19:01 ` Schmidl, Tobias
2022-08-10 7:10 ` Anton Mikanovich
2022-08-10 11:33 ` Anton Mikanovich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220802103921.1481725-1-felix.moessbauer@siemens.com \
--to=felix.moessbauer@siemens.com \
--cc=amikan@ilbers.de \
--cc=henning.schild@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.com \
--cc=tobiasschmidl@siemens.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox