yahoo-eng-team team mailing list archive

[Sankar Tanguturi <stanguturi@xxxxxxxxxx>]

Public bug reported:

Had a private chat conversation with Scott Moser (@smoser). As per his
instructions, logging this bug. We need to add 'cloud-init' dependency
for 'open-vm-tools' service.

This is how 'Guest Customization' works for the 'VMware' managed guests.

1. open-vm-tools service comes up and populates a 'customization' configuration file.
2. cloud-init service starts and waits for the 'customization config' file, reads it and applies the customization.

(1) should start before (2). Else, (2) will just block itself and not
find the config file. Everything was working fine. But due to recent
'systemd' changes done to 'cloud-init', 'cloud-init' service starts
early in the boot process before 'open-vm-tools' service. Due to this,
no customization actually happens.

Need to add the 'cloud-init' dependency for 'open-vm-tools' service so
that (1) always happens before (2).

Logging a bug.

Thanks
Sankar.

** Affects: cloud-init
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1667831

Title:
  cloud-init dependency for open-vm-tools service

Status in cloud-init:
  New

Bug description:
  Had a private chat conversation with Scott Moser (@smoser). As per his
  instructions, logging this bug. We need to add 'cloud-init' dependency
  for 'open-vm-tools' service.

  This is how 'Guest Customization' works for the 'VMware' managed
  guests.

  1. open-vm-tools service comes up and populates a 'customization' configuration file.
  2. cloud-init service starts and waits for the 'customization config' file, reads it and applies the customization.

  (1) should start before (2). Else, (2) will just block itself and not
  find the config file. Everything was working fine. But due to recent
  'systemd' changes done to 'cloud-init', 'cloud-init' service starts
  early in the boot process before 'open-vm-tools' service. Due to this,
  no customization actually happens.

  Need to add the 'cloud-init' dependency for 'open-vm-tools' service so
  that (1) always happens before (2).

  Logging a bug.

  Thanks
  Sankar.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1667831/+subscriptions