Created attachment 1701800 [details] Zipped folder with screenshots and logs. Description of problem: The Ubuntu Server 18.04 LTS (Bionic Beaver) Cloud Image v20190101 for x86_64 (3d5e74b) from ovirt-image-repo fails to boot when imported as a disk and attached to a VM. The boot screen gets stuck like the attached image ubuntu_launch_fail.png and after several minutes it shows the urandom warning as in image ubuntu_launch_fail.png. The host is running CentOS7 and is a Dell Poweredge R910 with Nehalem architecture. I have also attached the engine.log and the vdsm.log. How reproducible: Very Steps to Reproduce: 1. Import the Glance Disk (The Ubuntu Server 18.04 LTS (Bionic Beaver) Cloud Image v20190101 for x86_64 (3d5e74b)) to your iSCSI Storage domain. 2. Launch a VM with 4096 MB RAM, max memory 16384MB, 2 vCPUs, 'Use Cloud-Init/Sysprep' to set username, password, time zone and ssh keys, Console SPICE, and attach the Glance Instance Image. Everything else as default. 3. After Creation, click Run Once, verify Cloud Init is configured, wait till machine boots up, download SPICE console and wait till error message pops up. If I import the Ubuntu Server 18 iso to my iso domain, attach that to my VM and boot using the iso it works fine. I even installed it on a Virtual Disk that was attached to the VM.
The documentation text flag should only be set after 'doc text' field is provided. Please provide the documentation text and set the flag to '?' again.
Yeah, seems like an issue with that disk image. Sandro, who is the owner of releasing and maintaining those images on oVirt Glance?
(In reply to Arik from comment #2) > Yeah, seems like an issue with that disk image. > Sandro, who is the owner of releasing and maintaining those images on oVirt > Glance? it's the oVirt infra team, you can open a ticket to them on https://ovirt-jira.atlassian.net/browse/OVIRT
Hi and thanks for the report. Ubuntu images are imported to the image repo directly from cloud-images.ubuntu.com. From the screenshot it's not clear what exactly fails - looks like some service is failing to initialize. In nay case, I've just uploaded a fresh nightly build of Bionic, could you test it out and confirm if it comes up without issues? +------------------+--------------------------------------------------------------------------+ | Property | Value | +------------------+--------------------------------------------------------------------------+ | checksum | ed44b9745b8d62bcbbc180b5f36c24bb | | container_format | bare | | created_at | 2020-10-29T13:26:43Z | | disk_format | qcow2 | | id | b0040095-739e-48a3-a77c-dd97f2d1ad7a | | name | Ubuntu Server 18.04 LTS (Bionic Beaver) Cloud Image v20201016 for x86_64 | | owner | 186c4df6a4a44d52955c36c58afc788f | | protected | False | | size | 359464960 | +------------------+--------------------------------------------------------------------------+ Regards, Evgheni
While I'm at it, I've also bumped the Focal image version: +------------------+------------------------------------------------------------------------+ | Property | Value | +------------------+------------------------------------------------------------------------+ | checksum | c39172508ba84eba556697f5b84086a9 | | container_format | bare | | created_at | 2020-10-29T13:59:15Z | | disk_format | qcow2 | | id | b290d065-d85c-4fb7-a147-2c78fb93feaf | | name | Ubuntu Server 20.04 LTS (Focal Fossa) Cloud Image v20201016 for x86_64 | | owner | 186c4df6a4a44d52955c36c58afc788f | | protected | False | | size | 548274176 | +------------------+------------------------------------------------------------------------+ Could you please also test that it boots?
(In reply to Evgheni Dereveanchin from comment #5) > Could you please also test that it boots? Both images work fine for me. Thanks Evgheni. Can we drop the old one(s) then?
Great, thanks for testing. I'll remove the broken image and we can mark this BZ as Closed