← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1717611] [NEW] Azure: Azure datasource needs to wait forever for SSH pubkey to be dropped by waagent

 

Public bug reported:

In Azure SSH pubkeys are transported in a certificate through the wireserver protocol. When cloud-init is configured to use waagent, which is the current default, cloud-init will wait maxwait=60 seconds for waagent to drop the .crt files corresponding to the fingerprint that was mentioned in the ovf-env.xml.
We've had a couple of cases where the wireserver was flaky from more than 1 minute during provisioning which yielded a user without password or keys. These VM's are not usable without further action, we would rather have cloud-init wait forever for these .crt files to be provided. Azure VM provisioning will timeout and kill the VM when provisioning takes too long.

I'm working on a fix for this issue.

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

Title:
  Azure: Azure datasource needs to wait forever for SSH pubkey to be
  dropped by waagent

Status in cloud-init:
  New

Bug description:
  In Azure SSH pubkeys are transported in a certificate through the wireserver protocol. When cloud-init is configured to use waagent, which is the current default, cloud-init will wait maxwait=60 seconds for waagent to drop the .crt files corresponding to the fingerprint that was mentioned in the ovf-env.xml.
  We've had a couple of cases where the wireserver was flaky from more than 1 minute during provisioning which yielded a user without password or keys. These VM's are not usable without further action, we would rather have cloud-init wait forever for these .crt files to be provided. Azure VM provisioning will timeout and kill the VM when provisioning takes too long.

  I'm working on a fix for this issue.

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


Follow ups