RE: Bug: machine id is never generated

["Moessbauer, Felix" <felix.moessbauer@siemens.com>]

> From: Schild, Henning (T CED SES-DE) <henning.schild@siemens.com>
> Sent: Thursday, October 6, 2022 9:23 PM
> To: Moessbauer, Felix (T CED SES-DE) <felix.moessbauer@siemens.com>
> Cc: isar-users@googlegroups.com; Gylstorff, Quirin (T CED SES-DE)
> <quirin.gylstorff@siemens.com>; Schmidl, Tobias (T CED SES-DE)
> <tobiasschmidl@siemens.com>; Kiszka, Jan (T CED) <jan.kiszka@siemens.com>
> Subject: Re: Bug: machine id is never generated
> 
> Am Thu, 21 Jul 2022 17:41:07 +0200
> schrieb "Moessbauer, Felix (T CED SES-DE)"
> <felix.moessbauer@siemens.com>:
> 
> > 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
> 
> Seems that can also cause issues for NetworkManager where one can loose the
> network when a lease expires and a renew is due. I hope that
> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.co
> m%2Filbers%2Fisar%2Fcommit%2F693d76b8c06af&amp;data=05%7C01%7Cfeli
> x.moessbauer%40siemens.com%7C16b5eb33d35940dc0ad408daa79ddb88%7C
> 38ae3bcd95794fd4addab42e1495d55a%7C1%7C0%7C638006593671503174%7
> CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI
> 6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&amp;sdata=BAsqAoyxq1bY
> T%2BWBFBgLj9v4phYSe%2Bkppqv%2BpLtajUg%3D&amp;reserved=0 fixed that
> but just drop the error message here for completeness.
> 
> NetworkManager[526]: <error> [1665061214.9410] /etc/machine-id: no valid
> machine-id. Use fake one based on secret-key: ...

Hi Henning, yes, that's a typical pattern we see when the /etc/machine-id is not available.
But do you want to report a bug, or what is the intention of the statement from above?
The missing /etc/machine-id is fixed by the mentioned commit.
Did you try a build including this patch?

Felix

> 
> Henning
> 
> > 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:
> >
> > journalctl --grep machine --no-pager
> > -- Journal begins at Thu 2022-07-21 15:07:21 UTC, ends at Thu
> > 2022-07-21 15:35:20 UTC. -- Jul 21 15:07:21 test-image systemd[1]:
> > System cannot boot: Missing /etc/machine-id and /etc is mounted
> > read-only. Jul 21 15:07:21 test-image systemd[1]: 1) /etc/machine-id
> > exists and is populated. Jul 21 15:07:21 test-image systemd[1]: 2)
> > /etc/machine-id exists and is empty. Jul 21 15:07:21 test-image
> > systemd[1]: 3) /etc/machine-id is missing and /etc is writable. Jul
> > 21 15:07:24 test-image systemd[1]: Condition check resulted in Commit
> > a transient machine-id on disk being skipped.
> >
> > Maybe Quirin knows more, as he implemented the postproc removal in
> > 8b5e3f9. IIRC Jan also mentioned something that "rw" has to be added
> > to the kernel cmdline, but this looks like a workaround as well. For
> > the sake of completeness:
> >
> > cat /proc/cmdline
> > initrd=\initrd.img-5.10.0-16-amd64 LABEL=Boot
> > root=PARTUUID=9ad286e9-8df8-42c2-ac7d-0f2d7387d03d rootwait
> > console=tty0 console=ttyS0,115200
> >
> > IMO this is a pretty critical bug as it affects a ton of images.
> >
> > Best regards,
> > Felix
> >
> > --
> > Siemens AG, Linux Expert Center
> > Otto-Hahn-Ring 6, 81739 München, Germany
> >