Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1969562
Summary: | The created iso is not bootable | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Luca Giuzzi <luca.giuzzi> |
Component: | livecd-tools | Assignee: | Neal Gompa <ngompa13> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 34 | CC: | adam.stokes, bcl, bruno, dhuff, katzj, luca.giuzzi, metherid, ngompa13, vanmeeuwen+fedora |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | livecd-tools-28.3-1.el8 livecd-tools-28.3-1.fc33 livecd-tools-28.3-1.fc34 | Doc Type: | --- |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2021-06-28 00:31:30 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: |
Description
Luca Giuzzi
2021-06-08 15:48:33 UTC
I update my previous remarks. The image created with the patch boots in bios mode, but not in EFI mode. It seems that the cause is that shimx64.efi is copied with the name BOOTx64.efi but part of the script looks for the old name. Incidentally, a minimal example of the problem is with livecd-creator --config=/usr/share/doc/livecd-tools/livecd-fedora-minimal.ks The created image is not bootable. The relevant transcript is: Traceback (most recent call last): File "/usr/sbin/mkefiboot", line 168, in <module> main() File "/usr/sbin/mkefiboot", line 161, in main mkefiboot(opt.bootdir, opt.outfile, opt.label) File "/usr/sbin/mkefiboot", line 33, in mkefiboot mkdosimg(None, outfile, label=label, graft={'EFI/BOOT':bootdir}) File "/usr/lib/python3.9/site-packages/pylorax/imgutils.py", line 515, in mkdosimg mkfsimage("msdos", rootdir, outfile, size, mountargs=mountargs, File "/usr/lib/python3.9/site-packages/pylorax/imgutils.py", line 489, in mkfsimage with LoopDev(outfile, size) as loopdev: File "/usr/lib/python3.9/site-packages/pylorax/imgutils.py", line 355, in __init__ mksparse(self.filename, size) File "/usr/lib/python3.9/site-packages/pylorax/imgutils.py", line 143, in mksparse with open(outfile, "w") as fobj: FileNotFoundError: [Errno 2] No such file or directory: '/var/tmp/imgcreate-qr244tp5/is o-xlh3c83a/images/efiboot.img' Traceback (most recent call last): File "/usr/sbin/mkefiboot", line 168, in <module> main() File "/usr/sbin/mkefiboot", line 158, in main mkmacboot(opt.bootdir, opt.outfile, opt.label, opt.icon, opt.product, File "/usr/sbin/mkefiboot", line 45, in mkmacboot mkhfsimg(None, outfile, label=label, graft=graft, size=size) File "/usr/lib/python3.9/site-packages/pylorax/imgutils.py", line 530, in mkhfsimg mkfsimage("hfsplus", rootdir, outfile, size, mountargs=mountargs, File "/usr/lib/python3.9/site-packages/pylorax/imgutils.py", line 489, in mkfsimage with LoopDev(outfile, size) as loopdev: File "/usr/lib/python3.9/site-packages/pylorax/imgutils.py", line 355, in __init__ mksparse(self.filename, size) File "/usr/lib/python3.9/site-packages/pylorax/imgutils.py", line 143, in mksparse with open(outfile, "w") as fobj: FileNotFoundError: [Errno 2] No such file or directory: '/var/tmp/imgcreate-qr244tp5/iso-xlh3c83a/images/macboot.img' I apologize if I keep on adding comments, but now I am looking at mkefiboot (which perhaps is the true culprit). in /usr/lib/python3.9/site-packages/pylorax/imgutils.py there is the following line dev = runcmd_output(["losetup", "--find", "--show", outfile]).strip() which should call losetup with the proper parameters. However, even if outfile exists, it does fail. Actually, after I created a file out.img also this fails from pylorax.executils import runcmd, runcmd_output runcmd(["losetup","--find","--show","out.img"]).strip() while the shell command losetup --find --show ./out.img runs correctly FEDORA-EPEL-2021-28a6b0ea69 has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-28a6b0ea69 FEDORA-2021-d997907ec1 has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2021-d997907ec1 FEDORA-2021-b5ad7217c5 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-b5ad7217c5 FEDORA-2021-d997907ec1 has been pushed to the Fedora 33 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-d997907ec1` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-d997907ec1 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2021-b5ad7217c5 has been pushed to the Fedora 34 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-b5ad7217c5` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-b5ad7217c5 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-EPEL-2021-28a6b0ea69 has been pushed to the Fedora EPEL 8 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-28a6b0ea69 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-EPEL-2021-28a6b0ea69 has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-28a6b0ea69 FEDORA-2021-d997907ec1 has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2021-d997907ec1 FEDORA-2021-b5ad7217c5 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-b5ad7217c5 FEDORA-EPEL-2021-28a6b0ea69 has been pushed to the Fedora EPEL 8 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2021-d997907ec1 has been pushed to the Fedora 33 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-d997907ec1` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-d997907ec1 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2021-b5ad7217c5 has been pushed to the Fedora 34 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-b5ad7217c5` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-b5ad7217c5 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2021-d997907ec1 has been pushed to the Fedora 33 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2021-b5ad7217c5 has been pushed to the Fedora 34 stable repository. If problem still persists, please make note of it in this bug report. |