Thanks for the info Pengpeng.
The problem with that is that it will make cloud-init rather late.
Currently (this is the latest state after many fixup for just those
reasons of being too early/too late):
Note: Disambiguation of service names used below:
vgauth - open-vm-tools.vgauth.service
vmtoolsd - open-vm-tools.service
fs - systemd-remount-fs.service
tmp - systemd-tmpfiles-setup.service
cloud-init-l - cloud-init-local.service
cloud-init - cloud-init.service
fs -> vmtoolsd -> cloud-init-l
^
tmp --|
vgauth --|
apparmor --|
The problem is that all those services are meant to be super early and
therefore have DefaultDependencies=No.
Dbus on the other hand is not that super early and adding
After=dbus.service
Would move it way back in the initialization order which also you don't wan't
AFAIK (bug 1667831 to have open-vm-tools before cloud-init-local was by Sankar
from VMWare).
To be sure about it let me ask two questions:
- are your scripts triggered by cloud init
- if so in which config module/phase as I'm sure I have done cloud-init driven
hostname changed?
- OR are your scripts triggered by open-vm-tools directly?
@cloud-init Team:
- if we'd end up to make open-vm-tools after dbus.service that would move
cloud-init-local.service much later, could you outline the problems with that
OR if you are ok with it state so?
Furthermore lets talk in the call today to make sure we are on the same
page for this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1793715
Title:
VMWare Guest OS Customization will fail for Ubuntu 18.04 Server
LiveCD
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1793715/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
