- Newest
- Most votes
- Most comments
I looked into this and I think I've figured out what's happening. Canonical made a change to their cloud images in which "server" versions no longer include microcode related packages:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1938588
The microcode packages, (amd64-microcode and intel-microcode) change the format of the initrd when they're installed. The file can either be a single CPIO archive or a 2-part CPIO archive with 1 part being compressed:
https://unix.stackexchange.com/questions/505746/content-of-initramfs
One of these formats can cause the import service to return a client error. There are 2 general approaches for working around the issue:
-
If you'd like to use the base image for Ubuntu 20, simply use a EC2 ready AMI from Canonical. They publish their AMI account number to make it easy to find these official images: https://ubuntu.com/server/docs/cloud-images/amazon-ec2
-
If you have an existing image that has content and modifications you'd like to import, I would try to rebuild the initrd files by installing the microcode packages. Make sure to have a backup first, but then you can attempt to install the microcode packages:
sudo apt-get install -y dracut-core amd64-microcode intel-microcode
After the microcode packages are added the initrd should rebuild automatically in the correct format and resolve the issue, allowing the import to complete normally.
Relevant content
- asked 6 years ago
- asked 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 7 months ago
- AWS OFFICIALUpdated 8 months ago
Had this exact same error trying to import an ubuntu 20.04 image, created on Virtualbox, starting from the ubuntu focal-server-cloudimg-amd64.ova , using default kernel 5.4.0-121-generic.
Please help!