The patch has been merged in the nova code. Please note that the patch
implements the logic suggested in the comment #3:
if the file is present but empty nova will consider it as a missing file, then
it raises an exception.
--
You received this bug notification because you are a member of
I submitted a patch to nova to fix this issue:
https://review.openstack.org/202640
--
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
I'm unassigning myself; this isn't really a cloud image problem so much
as it is either a nova problem or a general Ubuntu problem; I'm not best
placed to solve either of these.
** Changed in: nova (Ubuntu)
Assignee: Daniel Watkins (daniel-thewatkins) = (unassigned)
--
You received this
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
** Changed in: nova (Ubuntu)
Importance: Undecided = High
** Changed in: nova (Ubuntu)
Status: New = Triaged
--
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:
Nova will use this file if present; however its empty on a stock vivid
cloud-image.
--
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
** Changed in: nova (Ubuntu)
Assignee: (unassigned) = Daniel Watkins (daniel-thewatkins)
--
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,
