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.

It appears that for s390x, creating iso is not possible (or optionnal ?), but the following dependencies are set none the less in the rear package:

   libburn
   libisoburn
   libisofs
   xorriso or genisoimage

Would it be possible not to have those set in the final rear package ?

Thanks for the report, I will have a look at addressing this in the next update. In the long term though I believe creating ISOs might be actually useful on S/390x (for booting LPARs). What do you think? Would that be an useful feature to add?

i just spoke with the customer behind ticket#03104120.
Being able to create iso on s390x might be interesting (so he has an other way of installing things) but is not something he is currently formally requesting.

Thanks. Is the customer using ReaR on a LPAR?

Note that if we add the ability to create ISOs, those dependencies will stay on the package, because they will not be unneeded anymore. Would that be a problem?

Yes, he is using Rear to backup/restore LPAR. 
Having the dependencies kept if they are actually used (in case a create iso features exist) is ok.

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 (rear 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:1966