yahoo-eng-team team mailing list archive

[Bastian Blank <1643688@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

The Azure data-source currently considers itself a networked one, as at
least part of the information is read via network. In consequence the
hostname is only known after network is already setup and a ifdown/ifup
cycle is initiated to update the network view of the hostname. This
cycle leads to a massive delay in boot time, at least if ipv6 setup is
requested.

Please split hostname setup out of the normal networked init run. The
information via the ovf file is known pretty early and without network.

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

Title:
  Azure should set hostname during init-local

Status in cloud-init:
  New

Bug description:
  The Azure data-source currently considers itself a networked one, as
  at least part of the information is read via network. In consequence
  the hostname is only known after network is already setup and a
  ifdown/ifup cycle is initiated to update the network view of the
  hostname. This cycle leads to a massive delay in boot time, at least
  if ipv6 setup is requested.

  Please split hostname setup out of the normal networked init run. The
  information via the ovf file is known pretty early and without
  network.

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