Bug 1225521 - Installation onto virtio disk fails due to missing by-id path
Summary: Installation onto virtio disk fails due to missing by-id path
Status: RESOLVED FIXED
: 1225615 (view as bug list)
Alias: None
Product: openSUSE Aeon
Classification: openSUSE
Component: Installation (show other bugs)
Version: Current
Hardware: x86-64 Other
: P2 - High : Normal
Target Milestone: ---
Assignee: Richard Brown
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-05-28 16:00 UTC by Tamara Schmitz
Modified: 2024-05-29 14:58 UTC (History)
1 user (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
tik.log (6.13 KB, text/x-log)
2024-05-28 16:00 UTC, Tamara Schmitz 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Tamara Schmitz 2024-05-28 16:00:58 UTC 
Created attachment 875168 [details]
tik.log

I tried to install openSUSE Aeon release candidate in a KVM/QEMU VM.
The installation raw image was added as a USB disk which is then made available as sda, the installation target was added as a VirtIO disk which is then made available as vda.

Booting the image and then pressing install yields in an error message:
"Could not find by-id representation of vda. Using original device /dev/vda."
Ignoring this error then shows:
"Given device /dev/disk/by-id/vda does not exist."
Then a popup tells me that the machine will shutdown again and store attached tik.log onto the installation raw image.
Comment 1 Richard Brown 2024-05-29 08:10:09 UTC 
https://github.com/sysrich/tik/pull/21 seeks to address this
Comment 2 Richard Brown 2024-05-29 08:12:36 UTC 
Setting High Priority

Thank you for the good bug report!
Comment 3 Richard Brown 2024-05-29 14:33:13 UTC 
Fixed in tik v1.0.5, otw to Factory
Comment 4 Richard Brown 2024-05-29 14:58:54 UTC 
*** Bug 1225615 has been marked as a duplicate of this bug. ***