systemd not considering cloud-init.target in vmware

Bug #1719321 reported by Daniel 'f0o' Preussker
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
cloud-init (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

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

description: updated
summary: - systemd not considering cloud-init.target on zesty in vmware
+ systemd not considering cloud-init.target in vmware
Revision history for this message
Scott Moser (smoser) wrote :

Hi,
thanks for taking the time to file a bug.
Could you please attach the output of:
  cloud-init collect-logs
(it will create a .tar.gz file in the local dir).

Then, set the bug state back to 'New'
Thanks.

Changed in cloud-init (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for cloud-init (Ubuntu) because there has been no activity for 60 days.]

Changed in cloud-init (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.