Bug 1973515
| Summary: | Kernel update in virt-customize causes an incorrect disk uuid in initrd (--update results in unbootable image) | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Lukáš Doktor <ldoktor> | ||||||
| Component: | dracut | Assignee: | dracut-maint-list | ||||||
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | unspecified | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 34 | CC: | dracut-maint-list, jonathan, rjones, zbyszek | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2022-06-07 20:44:34 UTC | Type: | Bug | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Bug Depends On: | |||||||||
| Bug Blocks: | 910269 | ||||||||
| Attachments: |
|
||||||||
|
Description
Lukáš Doktor
2021-06-18 04:21:21 UTC
Created attachment 1791948 [details]
Reproducer used to check various Fedoras
I used this script to find which Fedora version this occurred the first (first with --update, then added custom packages to try to reproduce that with F32 and F33 pkgs but no luck).
Note that RHEL8 images work well.
> virt-rescue --ro -a Fedora.qcow2
> # searching for the expected UUID
> ><rescue> findfs UUID=7486a5a4-47b9-478c-ab0c-44438c0b19ea
> /dev/sdb
In the virt-rescue appliance (which is the same environment
used by virt-customize), /dev/sdb is the appliance root.
/dev/sda which is the Fedora.qcow2 will have a different UUID.
If dracut is picking this UUID when run inside a chroot then
it's picking the wrong one. It should notice when it's run
inside a chroot and pick the UUID of the chrooted filesystem instead.
This message is a reminder that Fedora Linux 34 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '34'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 34 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed. I believe we fixed this one: https://bugzilla.redhat.com/show_bug.cgi?id=1945835#c24 https://github.com/rwmjones/guestfs-tools/commit/f2c0bf5387d094900de6420cb6502aa00d9c9b24 Fedora Linux 34 entered end-of-life (EOL) status on 2022-06-07. Fedora Linux 34 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. Thank you for reporting this bug and we are sorry it could not be fixed. |