Not all instance types have DMI

[mattgodbolt]

infra/init/log-instance-id.service

Line 10 in 8e99f14

ExecStart=cat /sys/devices/virtual/dmi/id/board_asset_tag

e.g. searching for this:

Jan 19 13:09:48Z ip-172-30-5-43 instance-id i-0088bda1b0868ad12
Jan 19 13:16:33Z ip-172-30-1-240 instance-id /usr/bin/cat: /sys/devices/virtual/dmi/id/board_asset_tag: No such file or directory
Jan 19 13:46:41Z ip-172-30-4-158 instance-id i-0d9f6fe7c79fe5075
Jan 19 15:28:26Z ip-172-30-1-40 instance-id /usr/bin/cat: /sys/devices/virtual/dmi/id/board_asset_tag: No such file or directory

[mattgodbolt]

Hopefully fixed by c4b2166

[mattgodbolt]

Needs checking but https://my.papertrailapp.com/events?q=program%3Ainstance-id looking good...

[mattgodbolt]

It wasn't "not ready" - for some instance types it would never turn up as older ones don't support DMI. For now 5b3e5ff limits us to only current generation, and I've reverted the wait change.

An alternative is to wait for networking and then curl an endpoint which I think works in more cases. Or accept instances with no logged out ID at startup, but it is useful information to have.