yahoo-eng-team team mailing list archive

[Balint Reczey <1919177@xxxxxxxxxxxxxxxxxx>]

@ddstreed Could you please look into this SRU candidate?

@gjolly What is the importance/urgency of landing this fix?

** Also affects: cloud-init (Ubuntu Hirsute)
   Importance: Undecided
       Status: New

** Also affects: systemd (Ubuntu Hirsute)
   Importance: Undecided
       Status: New

** Also affects: linux-azure (Ubuntu Hirsute)
   Importance: Undecided
       Status: New

** Changed in: systemd (Ubuntu)
       Status: Incomplete => Fix Released

** Changed in: linux-azure (Ubuntu Hirsute)
       Status: New => Invalid

** Changed in: cloud-init (Ubuntu Hirsute)
       Status: New => Incomplete

-- 
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/1919177

Title:
  Azure: issues with accelerated networking on Hirsute

Status in cloud-init:
  Incomplete
Status in cloud-init package in Ubuntu:
  Incomplete
Status in linux-azure package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in cloud-init source package in Hirsute:
  Incomplete
Status in linux-azure source package in Hirsute:
  Invalid
Status in systemd source package in Hirsute:
  New

Bug description:
  [General]

  On Azure, when provisioning a Hirsute VM with Accelerated Networking
  enabled, sometimes part of the cloud-init configuration is not
  applied.

  Especially, in those cases, the public SSH key is not setup properly.

  [how to reproduce]

  Start a VM with AN enabled:

  ```
  az vm create --name "$VM_NAME --resource-group "$GROUP" --location "UK South"  --image 'Canonical:0001-com-ubuntu-server-hirsute-daily:21_04-daily-gen2:latest' --size Standard_F8s_v2 --admin-username ubuntu --ssh-key-value "$SSH_KEY" --accelerated-networking
  ```

  After a moment, try to SSH: if you succeed, delete and recreate a new
  VM.

  [troubleshooting]

  To be able to connect into the VM, run:

  az vm run-command invoke -g "$GROUP" -n "$VM_NAME" --command-id RunShellScript --scripts "sudo -u ubuntu ssh-import-id $LP_USERNAME"
  ```

  In "/run/cloud-init/instance-data.json", I can see:
  ```
       "publicKeys": [
        {
         "keyData": "<my-pub-key>",
         "path": "/home/ubuntu/.ssh/authorized_keys"
        }
       ],
  ```

  as expected.

  [workaround]

  As mentioned, Azure allows the user to run command into the VM without
  SSH connection. To do so, one can use the Azure CLI:

  az vm run-command invoke -g "$GROUP" -n "$VM_NAME" --command-id
  RunShellScript --scripts "sudo -u ubuntu ssh-import-id $LP_USERNAME"

  This example uses "ssh-import-id" but it's also possible to just echo
  a given public key into /home/ubuntu/.ssh/authorized_keys

  NOTE: this will only solves the SSH issue, I do not know if this bug
  affects other things. If so the user would have to apply those things
  manually.

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