Re: Bug: machine id is never generated

["Schmidl, Tobias" <tobiasschmidl@siemens.com>]

Hi Felix,

Am Donnerstag, dem 21.07.2022 um 15:41 +0000 schrieb Moessbauer, Felix (T
CED SES-DE):
> Hi,
> 
> when booting plain ISAR images (with Debian11), the "/etc/machine-id" is
> never generated.
> This breaks a couple of services that depend on having the id.
> An example is the systemd-networkd with DHCP, leading to error messages
> like this one (and breaking networking):
> 
> systemd-networkd[277]: enp8s0: DHCP6 CLIENT: Failed to set identifier:
> No such file or directory
> 
> The error can manually be fixed by running "systemd-machine-id-setup",
> but this obviously does not work in embedded scenarios.
> 
> The root cause could be that /etc is read-only mounted when the first-
> boot-complete.target is reached.
> At least the logs indicate this:
> 

I've examined the same thing, for expand-on-first-boot, which would also
profit from a `ConditionFirstBoot=yes` in its service file. I've seen the
same pattern.

What I don't understand is that with a normal Debian the regeneration of
/etc/machine-id works without any problems. Somehow we have to differ
here.

Kind regards,

Tobias