Bug#918232: Cloud-init not setting public key on Azure portal when creating a virtual machine instance

[Damiaan Habets <dhabets@bluecatnetworks.com>]

Hi Thomas,

   The azure portal here: https://portal.azure.com/#home ; basically, we have a solution built on Debian Stretch. When deploying a VM of it in the portal, that VM doesn't end up with the public key that's passed to it using cloud-init. According to Azure/MS that's due to the cloud-init version that's being used. I hope that helps clarify things. If there's a better way, please let me know (

At the moment, we'll be looking into either upgrading cloud-init or fixing the specific bug in our image.


Thanks,
 
Damiaan Habets

On 2019-01-04, 3:13 PM, "Thomas Goirand" <zigo@debian.org> wrote:

    On 1/4/19 4:19 PM, Damiaan Habets wrote:
    > Package: cloud-init
    > Version: 0.7.9-2
    > 
    > Cloud-init not setting public key on Azure portal when creating a virtual machine instance. Appears to be fixed in: https://bugs.launchpad.net/cloud-init/+bug/1717611. Please upgrade cloud-init to cloud-init 18.4 or 18.5.
    > 
    > Using Debian Stretch, cloud-init 0.7.9-2. Note this works as expected with cloud-init 18.4.
    >  
    > Thanks,
    > Damiaan Habets
    
    Hi Damiaan,
    
    What is "Azure portal" exactly?
    
    Unfortunately, upgrading Stretch's cloud-init to 18.4 is going to be
    quite difficult, and I'd prefer if we found a solution that is more
    likely to be accepted by the Stable release team.
    
    Cheers,
    
    Thomas Goirand (zigo)