← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1823099] [NEW] Azure datasource sometimes fails to find wireserver endpoint

 

Public bug reported:

The Azure datasource needs to communicate with the "Wireserver" control
plane endpoint during provisioning. The IP address of the endpoint is
passed to the VM as option 245 via DHCP. Code to retrieve that address
is remarkably fragile across distros and in the face of changes users
can make in choosing or configuring a network manager. When the
datasource fails to find the endpoint address, provisioning will often
fail, leaving an uncommunicative VM behind. While error messages are
logged, the very nature of the problem (incorrect network setup and
incomplete ssh key provisioning, among other things) means those log
messages are difficult to access from outside the VM, and access to the
VM itself (e.g. via ssh) is often blocked.

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

Title:
  Azure datasource sometimes fails to find wireserver endpoint

Status in cloud-init:
  New

Bug description:
  The Azure datasource needs to communicate with the "Wireserver"
  control plane endpoint during provisioning. The IP address of the
  endpoint is passed to the VM as option 245 via DHCP. Code to retrieve
  that address is remarkably fragile across distros and in the face of
  changes users can make in choosing or configuring a network manager.
  When the datasource fails to find the endpoint address, provisioning
  will often fail, leaving an uncommunicative VM behind. While error
  messages are logged, the very nature of the problem (incorrect network
  setup and incomplete ssh key provisioning, among other things) means
  those log messages are difficult to access from outside the VM, and
  access to the VM itself (e.g. via ssh) is often blocked.

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


Follow ups