Conversation
There was a problem hiding this comment.
This does not concern the building of the ISO itself, but only the image use with the installer (ping @dupremathieu) and the qcow2 file used for guests.
So from my point of view, it would be more appropriate to apply this via the SEAPATH_RAW class rather than in the SEAPATH_COMMON class.
I agree. When FAI is used to generate an installation iso (build_iso.sh), the ssh host key and the machine-id are generated during the installation on target. When we generate an image directly (build_qcow2.sh and generate_seapath_image.sh) this generation is done in the "build" machine. So as @insatomcat said we should only apply your changes for the 2nd case. |
The generated image shipped with static machine-id and SSH host keys. The new file 70-first-boot ensures: - the first-boot semantics of systemd is executed - /etc/machine-id is generated and D-BUS machine id is linked to it - unique SSH host keys are generated Signed-off-by: Daniel Hofer <daniel.hofer@sprecher-automation.com>
|
Changes are made, sorry, I didn't notice the RAW class until now. |
Hello to All,
During development, I noticed the images generated would always have the same machine-id and SSH host keys once deployed. Among others, this lead to problems when MAC addresses were generated based on the machine-id.
The new file 70-first-boot ensures:
Best regards,
Daniel