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.
+++ This bug was initially created as a clone of Bug #1959598 +++
Description of problem:
RHEL has multiple tools for performing in place upgrades, as well as conversions from RHEL derivitive distributions. We need to ensure that for troubleshooting purposes, sosreport is collecting the log files from this tooling, as well as the status file from /etc/, as defined in https://issues.redhat.com/browse/RHELBU-1336
Version-Release number of selected component (if applicable):
Ideally, this change would be backported to sosreport in the following releases:
9.0
8.2, 8.3, 8.4, 8.5
7.9
6.10
--- Additional comment from Jake Hunsaker on 2021-05-11 21:35:54 UTC ---
Am I reading that correctly that the status files will be named `/etc/convert2rhel` and `/etc/leapp`? Or will it be something like `/etc/convert2rhel-$date` or similar?
Is there a full list of convert2rhel/leapp env vars that should be captured as well?
--- Additional comment from Jose Castillo on 2021-05-12 07:34:17 UTC ---
Also, I can see that in the documentation customers can specify an user and a password:
# convert2rhel --username <username> --password <password> --pool <pool_id>
Does this get recorded in the logs we already capture:
"/var/log/convert2rhel/convert2rhel.log",
"/var/log/convert2rhel/rpm_va.log"
Or in the configuration files perhaps?
The file to newly collect is /etc/migration-results.
When to collect: when at least one of the following packages is installed: leapp, leapp-repository.
There already is a plugin for leapp: https://github.com/sosreport/sos/pull/1753/files
It seems to me it could be extended to gather this new file.
(In reply to Pavel Moravec from comment #6)
> This will land in 8.6 and 9.0 via candidate packages:
> https://people.redhat.com/pmoravec/sos-4.2-15/
.. and it already happened, so closing as fixed in current release (8.6/9.0).