[Bug 1413293] Re: Unable to start instances, empty /etc/machine-id file.
Daniel Watkins
daniel.watkins at canonical.com
Thu Jan 22 11:28:49 UTC 2015
This problem (should) disappear with systemd; it takes care of
populating /etc/machine-id on first boot, though it does need the file
to exist and be empty[0].
So we should do one (or more) of:
- teach nova that an empty /etc/machine-id is equivalent to a missing one,
- introduce an Upstart job which will populate /etc/machine-id on boot, or
- wait.
[0] systemd needs /etc/machine-id to exist if /etc is read-only, so it can mount (a temporary) /run/machine-id over it. Once /etc becomes writable, the temporary file is made persistent.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1413293
Title:
Unable to start instances, empty /etc/machine-id file.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1413293/+subscriptions
More information about the Ubuntu-server-bugs
mailing list