Bug 1360624 – sosreport should collect detailed yum history

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1360624 - sosreport should collect detailed yum history

Summary:	sosreport should collect detailed yum history

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Enterprise Linux 7
Classification:	Red Hat
Component:	sos (Show other bugs)
Sub Component:
Version:	7.2
Hardware:	Unspecified Unspecified

Priority	unspecified Severity unspecified
Target Milestone:	rc
Target Release:	---
Assigned To:	Pavel Moravec
QA Contact:	Anna Khaitovich
Docs Contact:

URL:	https://github.com/sosreport/sos/pull...
Whiteboard:
Keywords:

Depends On:
Blocks:	1360621
	Show dependency tree / graph

Reported:	2016-07-27 03:40 EDT by Yedidyah Bar David
Modified:	2018-02-01 21:22 EST (History)
CC List:	9 users (show)

See Also:	1360623
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 19:08:12 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHBA-2017:2203	normal	SHIPPED_LIVE	sos bug fix and enhancement update	2017-08-01 15:41:56 EDT

Groups: None (edit)

Description Yedidyah Bar David 2016-07-27 03:40:30 EDT

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 04:07:02 EDT

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

Comment 2 Bryn M. Reeves 2016-07-27 05:45:08 EDT

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 16:15:13 EDT

POSTed to upstream as  	7c428d1

Comment 7 errata-xmlrpc 2017-08-01 19:08:12 EDT

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

Note You need to log in before you can comment on or make changes to this bug.