|
Bugzilla – Full Text Bug Listing |
| Summary: | Installation onto virtio disk fails due to missing by-id path | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Aeon | Reporter: | Tamara Schmitz <tamara.schmitz> |
| Component: | Installation | Assignee: | Richard Brown <rbrown> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P2 - High | CC: | igonzalezsosa |
| Version: | Current | ||
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | tik.log | ||
https://github.com/sysrich/tik/pull/21 seeks to address this Setting High Priority Thank you for the good bug report! Fixed in tik v1.0.5, otw to Factory *** Bug 1225615 has been marked as a duplicate of this bug. *** |
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.