Bug 1360623 - sosreport should collect detailed dnf history
Summary: sosreport should collect detailed dnf history
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: sos
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Bryn M. Reeves
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 1360621
TreeView+ depends on / blocked
 
Reported: 2016-07-27 07:39 UTC by Yedidyah Bar David
Modified: 2017-02-23 16:29 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-02-23 16:29:58 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github sosreport sos pull 857 0 None None None 2017-02-23 16:29:57 UTC
Red Hat Bugzilla 1360624 0 unspecified CLOSED sosreport should collect detailed yum history 2021-02-22 00:41:40 UTC

Internal Links: 1360624

Description Yedidyah Bar David 2016-07-27 07:39:39 UTC
Description of problem:

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

dnf allows seeing exactly what happened in each transaction.

We should collect that.

Comment 1 Yedidyah Bar David 2016-07-27 07:43:01 UTC
A patch to do that was pushed to upstream:

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

Comment 2 Bryn M. Reeves 2016-07-27 09:44:31 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 3 Sandro Bonazzola 2017-02-23 16:29:58 UTC
The problem described has been handled upstream in https://github.com/sosreport/sos/pull/857


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