Bug 1959782

Summary:	[6.10.z] sosreport needs to collect data about conversions and upgrades
Product:	Red Hat Enterprise Linux 6	Reporter:	Terry Bowling <tbowling>
Component:	sos	Assignee:	Filip Krska <fkrska>
Status:	CLOSED ERRATA	QA Contact:	Radek Duda <rduda>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	6.10	CC:	agk, bmr, cww, jcastillo, jhunsaker, mhradile, mkluson, plambri, pmoravec, rduda, sbradley, theute, upgrades-and-supportability
Target Milestone:	rc	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:	sos-3.2-63.el6_10.6	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1959598	Environment:
Last Closed:	2022-03-24 16:30:12 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1959598, 1985551, 1985552, 1992957
Bug Blocks:	1959779, 1959781

Description Terry Bowling 2021-05-12 11:00:32 UTC

+++ 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?

Comment 1 Pavel Moravec 2021-07-26 13:13:01 UTC

Technically, the request is to add a new trivial plugin per PR:

https://github.com/sosreport/sos/pull/2627

leaving on Filip if it is worth backporting to RHEL6 as a z-stream(?) / async errata.

Comment 5 Radek Duda 2022-03-23 15:25:09 UTC

Verified manually on x86_64 RHEL-6.10 mocking the migration-results file.

NEW:
#rpm -q sos
sos-3.2-63.el6_10.6.noarch
#sosreport --list-plugins | grep migration
 migration_results    Information about conversions and upgrades
# touch /etc/migration-results

# sosreport --batch -vvv
. . .
# tar -tf /tmp/sosreport-rduda-1mt-rhel-6-10-updates-20201110-17-6948-2022-03-23-14-49-20220323111628.tar.xz | grep migration
sosreport-rduda-1mt-rhel-6-10-updates-20201110-17-6948-2022-03-23-14-49-20220323111628/etc/migration-results
sosreport-rduda-1mt-rhel-6-10-updates-20201110-17-6948-2022-03-23-14-49-20220323111628/proc/sys/kernel/sched_migration_cost
sosreport-rduda-1mt-rhel-6-10-updates-20201110-17-6948-2022-03-23-14-49-20220323111628/proc/sys/kernel/timer_migration


OLD:
# rpm -q sos
# sos-3.2-63.el6_10.4.noarch
# sosreport -o migration_results --batch --build
sosreport (version 3.2)
 a non-existing plugin (migration_results) was specified in the command line

# sosreport --batch -vvv
. . .
# tar -tf /tmp/sosreport-rduda-1mt-rhel-6-10-updates-20201110-17-6948-2022-03-23-14-49-20220323112104.tar.xz | grep migration
sosreport-rduda-1mt-rhel-6-10-updates-20201110-17-6948-2022-03-23-14-49-20220323112104/proc/sys/kernel/sched_migration_cost
sosreport-rduda-1mt-rhel-6-10-updates-20201110-17-6948-2022-03-23-14-49-20220323112104/proc/sys/kernel/timer_migration

Comment 8 errata-xmlrpc 2022-03-24 16:30:12 UTC

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 (sos 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/RHEA-2022:1060