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.

When running this command
# leapp upgrade --debug

It doesn't create /var/log/leapp/dnf-debugdata/ directory containing transaction debug data.

Reported by: muhammad.khalil

https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/upgrading_to_rhel_8/troubleshooting_upgrading-to-rhel-8#annotations:240be220-010b-4c16-8ffc-475a65d054ed

Hi,
the doc is correct. It tells:
===
If a problem occurs during downloading RPM packages, examine transaction debug data located in the /var/log/leapp/dnf-debugdata/ directory.
===

In case of customer I guess that problem occured much earlier - before we tried to download RPMs; to be clear, before we have been able to calculate the upgrade transaction. So there are no data that would be used to obtain something about problems with calculation of the upgrade transaction and as that, the directory is empty. The most probably, customer was not able to obtain even the metadata about target (RHEL 8) repositories.

So far, doc is exact here from my POV.

Correction: *... and as that, the directory is not created as it would be only empty. ...*

Thanks, Petr, for the expertise. There appears to be nothing I can do at this point.