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.

Created attachment 702620 [details]
Installation system log

Description of problem:
The rhel7 dvd iso installation image made by mkisofs cannot be used for installation, the rhel7 installation progress will stopped to dracut interactive command line.
No such problem with rhel5/rhel6 releases.

Version-Release number of selected component (if applicable):
mkisofs-2.01-10.7.el5
RHEL-7.0-20130222.0-Server-x86_64

How reproducible:
100%

Steps to Reproduce:
1. Prepare a standard rhel7 installation iso image(I built it by jigdo-lite and it can be used for installation).
2. Mount RHEL-7.0-20130222.0-Server-x86_64-dvd1.iso to a temp directory.
3. Copy the content of the temp directory to a new temp directory.
4. Assign write permission to the files under isolinux directory.
5. Make bootable iso on the new temp dir with command:
mkisofs -o ../rhel7-mkisofs.iso -b isolinux.bin -c boot.cat -no-emul-boot -boot-load-size 4 -boot-info-table -R -J -v -T .


actual result:
The installation progress stopped to a dracut command line.


expect result:
The rhel7 can be installed successfully by the new iso image.


additional info:
Please check the attachment for installation system log.

Your command is missing crucial "-volid" parameter. Is this really a bug in mkisofs? Should the boot process work without explicitly setting proper volume ID?
Does -volid solve your problem?

(In reply to comment #2)
> Your command is missing crucial "-volid" parameter. Is this really a bug in
> mkisofs? Should the boot process work without explicitly setting proper
> volume ID?
> Does -volid solve your problem?

  Yes, it solved as what you said. Weird, i can do this without volid for all of rhel5&rhel6 iso iamges, so i suppose that rhel7 can be use the same manner.
  Anyway, i am very appreciative of you help, thanks.

See isolinux/isolinux.cfg: append initrd=initrd.img inst.stage2= ...

In RHEL7, volume ID must match with "inst.stage2=".
RHEL5 and RHEL6 versions do not mention any "inst.stage2=". Do not ask me why. Dracut has changed, anaconda has changed, sysvinit/upstart/systemd has changed.

Closing as NOTABUG.

This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.