| 2017-09-25 14:57:13 |
Daniel 'f0o' Preussker |
description |
It seems that cloud-init under Zesty is broken when run from vmware.
It works fine if I trigger it manually via `systemd start cloud-init.service` and it will find the datasource correctly and set things up accordingly but it fails to start during bootup.
There's absolutely no sign of it being executed upon boot. No logs/journal, No temp files, Nothing.
Steps:
1) Fresh ISO install of Zesty without user (only root).
2) apt-get update && apt-get upgrade -y && apt-get install cloud-init && systemctl enable cloud-init.service (no output, seems already enabled)
3) *cleanup, like history and ssh-keys*
4) Snapshot, Clone, Boot
--- Cloned VM
1) Boots up
2) No cloud-init bootup.
This is 100% reproducible for me. |
It seems that cloud-init is broken when run from vmware.
It works fine if I trigger it manually via `systemd start cloud-init.service` and it will find the datasource correctly and set things up accordingly but it fails to start during bootup.
There's absolutely no sign of it being executed upon boot. No logs/journal, No temp files, Nothing.
Steps:
1) Fresh ISO install of Zesty or Xenial without user (only root).
2) apt-get update && apt-get upgrade -y && apt-get install cloud-init && systemctl enable cloud-init.service (no output, seems already enabled)
3) *cleanup, like history and ssh-keys*
4) Snapshot, Clone, Boot
--- Cloned VM
1) Boots up
2) No cloud-init bootup.
This is 100% reproducible for me.
//Edit: Same happens on Xenial |
|
