question

NancyAdams-6244 avatar image
0 Votes"
NancyAdams-6244 asked vipullag-MSFT commented

Ubuntu 20.04 VM not accessible after ASM to ARM migration

have an Azure VM running Ubuntu 20.04 that was migrated from ASM (cloud service) to ARM and is now not accessible.

This VM was running in a Cloud Service under the Classic model (ASM) and was migrated into an existing ARM network.
Migration was successful and without any errors. VM created by the migration process starts fine but the issue seems to be the Network Interface and cloud-init/Netplan:

Here is the snippet from boot log:

[ 17.259047] cloud-init[841]: Cloud-init v. 21.4-0ubuntu1~20.04.1 running 'init' at Wed, 26 Jan 2022 13:15:05 +0000. Up 17.18 seconds.
[ 17.263428] cloud-init[841]: ci-info: +++++++++++++++++++++++++++Net device info++++++++++++++++++++++++++++
[ 17.266924] cloud-init[841]: ci-info: +--------+-------+-----------+-----------+-------+-------------------+
[ 17.275372] cloud-init[841]: ci-info: | Device | Up | Address | Mask | Scope | Hw-Address |
[ 17.279379] cloud-init[841]: ci-info: +--------+-------+-----------+-----------+-------+-------------------+
[ 17.283570] cloud-init[841]: ci-info: | eth0 | False | . | . | . | 00:22:48:03:c6:ef |
[ 17.287710] cloud-init[841]: ci-info: | lo | True | 127.0.0.1 | 255.0.0.0 | host | . |
[ 17.291555] cloud-init[841]: ci-info: | lo | True | ::1/128 | . | host | . |
[ 17.297514] cloud-init[841]: ci-info: +--------+-------+-----------+-----------+-------+-------------------+
[ 17.301354] cloud-init[841]: ci-info: +++++++++++++++++++Route IPv6 info+++++++++++++++++++
[ 17.304512] cloud-init[841]: ci-info: +-------+-------------+---------+-----------+-------+
[ 17.307952] cloud-init[841]: ci-info: | Route | Destination | Gateway | Interface | Flags |
[ 17.311051] cloud-init[841]: ci-info: +-------+-------------+---------+-----------+-------+
[ 17.314155] cloud-init[841]: ci-info: +-------+-------------+---------+-----------+-------+
[ 17.317365] cloud-init[841]: 2022-01-26 13:15:05,721 - stages.py[WARNING]: Failed to rename devices: [nic not present] Cannot rename mac=00:0d:3a:34:fe:cf to eth0, not available.
[ 17.414216] blk_update_request: I/O error, dev fd0, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0

It appears to be the same error message as described here:

https://serverfault.com/questions/922128/changing-network-interface-of-a-virtual-machine-with-ubuntu-18-04/922253

How can I fix this?
I tried:
-Creating and assigning new Network Interfaces through Azure Portal
-Creating a new VM from the copy of the OS disk
-Redeploying the VM

but no luck. The Network Interface does not get initialized.

The VM starts and I can connect to Serial Console but I don't have password authentication enabled.
I think I can mount the OS disk as a data disk and access it but what would I need to change to allow cloud-init/Netplan to initialize Network Interface correctly in this scenario?

azure-virtual-machines-migration
· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

@NancyAdams-6244

Thanks for reaching out to Microsoft Q&A Platform.

This issue needs deeper investigation. Support team will be able to check and help on this. I would recommend you to open a azure support case.

If you don't have the ability to open a technical support ticket, please let me know to help you further on this.

0 Votes 0 ·

0 Answers