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.

Description of problem:

I was looking at the instructions for burning to CD/DVD and noticed that the step for checking that cdrecord is installed is:

rpm -q cdrecord

followed by:

yum install cdrecord

To install it. On my RHEL 6 VM however I can see that cdrecord has been replaced, there is a wrapper to libburn which replaces it called cdrskin. So the steps would be to install the cdrskin package, and use the cdrskin binary to burn the disk.

Just to make life even more complicated, yum install cdrecord now installs a cdrecord binary that serves a completely different purpose to what people are historically used to. So we need to clear this up in the documentation.

http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Hypervisor_Deployment_Guide/sect-Deployment_Guide-Preparing_Red_Hat_Enterprise_Virtualization_Hypervisor_installation_media-Preparing_a_RHEV_Hypervisor_from_a_CD_ROM_or_DVD.html

Not 100% sure but I think wodim is the cdrecord replacement, functionality wise. An alternative in graphical environments is brasero but this assumes a lot about the machine being used.

Created attachment 570422 [details]
Patch for wodim/cdrecord.

Patch I applied to the install guide, basically all cdrecord references become wodim, plus a few minor edits.

Something equivalent will need to happen in the Hypervisor Deployment Guide.