Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
.`osbuild` no longer fails to build an ISO image bigger than 4GB
Image Builder users can create a customized image by adding additional packages. If the total size of the packages and their dependencies exceeded 4GB size, users of RHEL 8.5 and earlier releases would see the following error:
----
ubprocess.CalledProcessError: Command '['/usr/bin/xorrisofs', '-verbose', '-V', 'RHEL-8-5-0-BaseOS-x86_64', '-sysid', 'LINUX', '-isohybrid-mbr', '/usr/share/syslinux/isohdpfx.bin', '-b', 'isolinux/isolinux.bin', '-c', 'isolinux/boot.cat', '-boot-load-size', '4', '-boot-info-table', '-no-emul-boot', '-rock', '-joliet', '-eltorito-alt-boot', '-e', 'images/efiboot.img', '-no-emul-boot', '-isohybrid-gpt-basdat', '-o', '/run/osbuild/tree/installer.iso', '/run/osbuild/inputs/tree']' returned non-zero exit status 32.
----
The problem happened because the ISO 9660 Level Of Interchange `-isolevel 3` argument was not passed to the `xorrisofs` command. To work around the problem, users had to permanently alter the ISO level value to 3.
With the RHEL 8.6 release, the problem has been fixed, and users no longer need to permanently alter the ISO level value.
Christian, does it make sense to set the isolevel to 3 in the image definition? I checked RHEL 8.5 boot and "DVD" isos and they seem to be level 3.
$ iso-info rhel-8.5-x86_64-boot.iso
iso-info version 2.1.0 x86_64-redhat-linux-gnu
Copyright (c) 2003-2005, 2007-2008, 2011-2015, 2017 R. Bernstein
This is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE.
__________________________________
ISO 9660 image: rhel-8.5-x86_64-boot.iso
Application : GENISOIMAGE ISO 9660_HFS FILESYSTEM CREATOR (C) 1993 E.YOUNGDALE
System : LINUX
Volume : RHEL-8-5-0-BaseOS-x86_64
Joliet Level: 3
$ iso-info rhel-8.5-x86_64-boot.iso
iso-info version 2.1.0 x86_64-redhat-linux-gnu
Copyright (c) 2003-2005, 2007-2008, 2011-2015, 2017 R. Bernstein
This is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE.
__________________________________
ISO 9660 image: rhel-8.5-x86_64-boot.iso
Application : GENISOIMAGE ISO 9660_HFS FILESYSTEM CREATOR (C) 1993 E.YOUNGDALE
System : LINUX
Volume : RHEL-8-5-0-BaseOS-x86_64
Joliet Level: 3
Comment 2Christian Kellner
2022-02-21 10:55:44 UTC
Ondřej, for sure! I am surprised we are not doing so already!
Hi,
the file size problem was indeed caused by the fact that the ISO 9660
Level Of Interchange was not set to 3 (= multi-extent).
But the information from iso-info (companion of libcdio) about other
ISOs:
Joliet Level: 3
does not tell that -iso-level >=3 was applied when those ISOs were made.
The Joliet level is rather about character sets. libcdio gets this info
from the Joliet superblock (SVD).
joliet.pdf "Identifying an ISO 9660 SVD as Unicode (UCS-2)" talks of
ISO 2022, which seems to define escape sequences for switching between
UCS-2 planes (https://en.wikipedia.org/wiki/Universal_Coded_Character_Set).
The ISO 9660 Level Of Interchange is not announced by any volume
descriptor. It can only be detected by looking in the tree of directory
records for more than one consequtive records with the same file name.
Together they describe a multi-extent data file which is allowed only if
level 3 is enabled at ISO production time.
ISO level 3 is ok if the ISO shall be read by Linux or MS-Windows.
Other systems might habe problems with multi-extent files. (But xorriso
is able to extract them on any system where it can be built.)
Have a nice day :)
Thomas
Comment 11Alexander Todorov
2022-03-08 11:16:14 UTC
From https://gitlab.com/osbuild/ci/osbuild-composer/-/jobs/2174390852:
Running test: regression-bigiso.sh
Passed tests: regression-excluded-dependency.sh regression-include-excluded-packages.sh regression-composer-works-behind-satellite.sh regression-composer-works-behind-satellite-fallback.sh regression-bigiso.sh
Moving to VERIFIED.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (osbuild-composer bug fix and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2022:1841