Install with virtio disk fails due to unknown serial
Bug #1743631 reported by
Joshua Powers
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
curtin |
Invalid
|
Undecided
|
Unassigned | ||
subiquity |
Fix Released
|
Undecided
|
Unassigned | ||
probert (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Description:
Using the daily live server ISO (subiquity), creating a VM with virt-manager and attaching a virt-io disk results in an install failure. Based on a conversation in #curtin this is because probert is not getting a serial number and uses a default value of "Unknown serial". Subiquity needs to supply the path to curtin instead.
Subiquity log:
https:/
Curtin log:
https:/
Error message:
ValueError: no disk with serial 'Unknown_Serial' found
tags: | added: id-5a712e2eedc3c79fe655ecf3 |
Changed in subiquity: | |
status: | New → Fix Released |
Changed in probert (Ubuntu): | |
status: | Confirmed → Fix Released |
To post a comment you must log in.
when installing with curtin, disks can be specified via the 'path' key or 'serial'.
When specifying 'serial', curtin will attempt to locate the target disk by glob;ing in /dev/disk/ by-id/* serial* to find the disk that matches the specified serial number.
In this instance, the virtio disk was not provided with a serial number, probert appears to have provided a serial number of 'Unknown_Serial' which was not found in /dev/disk/by-id/ on the install source machine.
subiquity likely needs to determine if it can use 'serial' or 'path' based on the probert information. Probert may need to omit serial value, or use a 'none' value instead of 'Unknown_Serial'.
If we're feeling lucky, we could also file a qemu bug to see if upstream is interested in having virtio disks have a default serial number like IDE devices do (as well as network devices which get a default mac address).