Bug 1360624

Summary:	sosreport should collect detailed yum history
Product:	Red Hat Enterprise Linux 7	Reporter:	Yedidyah Bar David <didi>
Component:	sos	Assignee:	Pavel Moravec <pmoravec>
Status:	CLOSED ERRATA	QA Contact:	Anna Khaitovich <akhaitov>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.2	CC:	agk, akhaitov, bmr, gavin, isenfeld, mhradile, mkolbas, plambri, sbradley
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
URL:	https://github.com/sosreport/sos/pull/857
Whiteboard:
Fixed In Version:	sos-3.4-1.el7	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-08-01 23:08:12 UTC	Type:	Bug
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:
Bug Blocks:	1360621

Description Yedidyah Bar David 2016-07-27 07:40:30 UTC

Description of problem:

Sometimes yum.log isn't enough to understand what happened when debugging an issue based on a sosreport.

yum allows seeing exactly what happened in each transaction.

We should collect that.

Comment 1 Pavel Moravec 2016-07-27 08:07:02 UTC

ACK to 7.4, one minor question from me in the upstream PR

Comment 2 Bryn M. Reeves 2016-07-27 09:45:08 UTC

It's considered helpful to QE and others working on the bug to include all the sections of the bugzilla template when filing bugs - although things like how to reproduce, and test may seem obvious when entering the bug it isn't always the case months down the line when people are trying to figure things out close to deadlines.

I've added some comments to the upstream pull request but once that is settled it would be good to add some information here on testing and verifying the new features.

Comment 4 Pavel Moravec 2017-03-12 20:15:13 UTC

POSTed to upstream as  	7c428d1

Comment 7 errata-xmlrpc 2017-08-01 23:08: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, 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-2017:2203