Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/index.php/Reporting_Bug_Guidelines

Do NOT report bugs when a package is just outdated, or it is in Unsupported. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#61862 - [systemd] generates machine-id which is not unique for containers

Attached to Project: Arch Linux
Opened by Justin Capella (justincapella) - Monday, 25 February 2019, 21:01 GMT
Last edited by Eli Schwartz (eschwartz) - Monday, 25 February 2019, 21:51 GMT
Task Type Bug Report
Category Packages: Core
Status Assigned
Assigned To Dave Reisner (falconindy)
Christian Hesse (eworm)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No

Details

Description:
systemd-machine-id-setup does not generate unique id, causes problems with dhcp clients that use this as a client-identifier when dhcp server uses for addressing, causing vms/containers and the like to often be issued the same address causing connectivity / ARP problems.


Additional info:
systemd-firstboot --setup-machine-id; works to create a unique / varying id (assuming no /etc/machine-id exists), no idea why two binaries exist for the seemingly the same purpose... but the currently used one causes me grief.


Steps to reproduce:
Install a couple vms or archlinux containers etc, see that /etc/machine-id is not unique
This task depends upon

Comment by Justin Capella (justincapella) - Monday, 25 February 2019, 21:02 GMT
Ugh is there really no way for the submitter to edit a task, and why is the title default value accepted ;\
Comment by Eli Schwartz (eschwartz) - Monday, 25 February 2019, 21:51 GMT
  • Field changed: Summary ([systemd] PLEASE ENTER SUMMARY → [systemd] generates machine-id which is not unique for containers)
  • Field changed: Status (Unconfirmed → Assigned)
  • Task assigned to Dave Reisner (falconindy), Christian Hesse (eworm)
Originally fixed in  FS#40131  to use systemd-firstboot, reverted entirely in  FS#41711  which used uuidgen due to the bug that was eventually fixed in https://github.com/systemd/systemd/commit/07a60cc13c48c5f79616b07aad2808bfe809de22, and restored... to systemd-machine-id-setup... in systemd 218-2.

In the spirit of  FS#40131  I guess it makes sense to use systemd-firstboot.

Loading...