yahoo-eng-team team mailing list archive

[Bastian Blank <1538522@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Hi

cloud-init calls "service walinuxagent start" in the Azure data source
during "init" phase.

Currently walinuxagent.service in Ubuntu 15.10 specifies:
| After=cloud-final.service
This asks systemd to start if much later, after the "final" phase.

New enough systemd version as available in Ubuntu 15.10 and Debian
Stretch will just ignore the relation, as it is a deadlock and start the
service in this place. Older version as in Debian Jessie will block the
whole boot.

Is there a reason to explicitely start walinuxagent instead of relying
on order in systemd?

Bastian

** 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/1538522

Title:
  Calls "service walinuxagent start" in Azure data source

Status in cloud-init:
  New

Bug description:
  Hi

  cloud-init calls "service walinuxagent start" in the Azure data source
  during "init" phase.

  Currently walinuxagent.service in Ubuntu 15.10 specifies:
  | After=cloud-final.service
  This asks systemd to start if much later, after the "final" phase.

  New enough systemd version as available in Ubuntu 15.10 and Debian
  Stretch will just ignore the relation, as it is a deadlock and start
  the service in this place. Older version as in Debian Jessie will
  block the whole boot.

  Is there a reason to explicitely start walinuxagent instead of relying
  on order in systemd?

  Bastian

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