Bug 1360621 - log-collector should collect detailed yum/dnf history
Summary: log-collector should collect detailed yum/dnf history
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-log-collector
Classification: oVirt
Component: SOS-plugins
Version: 4.0.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ovirt-4.3.0
: 4.3.0
Assignee: Douglas Schilling Landgraf
QA Contact: Petr Matyáš
URL:
Whiteboard:
Depends On: 1360623 1360624
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-07-27 07:38 UTC by Yedidyah Bar David
Modified: 2019-03-13 16:37 UTC (History)
6 users (show)

Fixed In Version: ovirt-log-collector-4.3.0_beta1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-03-13 16:37:44 UTC
oVirt Team: Integration
Embargoed:
rule-engine: ovirt-4.3+
dnecpal: testing_plan_complete-
ylavi: planning_ack+
sbonazzo: devel_ack+
pstehlik: testing_ack+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 86675 0 master MERGED ovirt-log-collector: Include yum/dnf history 2018-11-21 13:48:26 UTC

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

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

yum and dnf allow seeing exactly what happened in each transaction.

We should collect that.

Comment 1 Yaniv Kaul 2017-06-06 20:01:26 UTC
(In reply to Yedidyah Bar David from comment #0)
> Description of problem:
> 
> Sometimes yum/dnf.log isn't enough to understand what happened when
> debugging an issue based on a sosreport.
> 
> yum and dnf allow seeing exactly what happened in each transaction.

Can you expand on this?

> 
> We should collect that.

Comment 2 Yedidyah Bar David 2017-06-07 05:47:14 UTC
(In reply to Yaniv Kaul from comment #1)
> (In reply to Yedidyah Bar David from comment #0)
> > Description of problem:
> > 
> > Sometimes yum/dnf.log isn't enough to understand what happened when
> > debugging an issue based on a sosreport.
> > 
> > yum and dnf allow seeing exactly what happened in each transaction.
> 
> Can you expand on this?

This is already covered in dep bugs on sosreport.

Current bug is on ovirt-log-collector, and is aimed at activating the options added to sosreport to make sure we actually collect them by default.

Comment 3 Sandro Bonazzola 2017-10-12 12:56:28 UTC
Lev, dependent bugs on sos are closed, can you check if we can move on with this bug?

Comment 4 Lev Veyde 2017-11-20 12:42:46 UTC
(In reply to Sandro Bonazzola from comment #3)
> Lev, dependent bugs on sos are closed, can you check if we can move on with
> this bug?

Yes, I think we can.

Comment 5 Douglas Schilling Landgraf 2018-01-05 18:47:52 UTC
PR: https://github.com/oVirt/ovirt-log-collector/pull/2

Additionally, in my system adding '-k', 'yum.yum-history-info=on' increased the time to collect the data, so if users want to use this feature, use --package-manager-history.

# cat /etc/redhat-release 
Red Hat Enterprise Linux Server release 7.5 Beta (Maipo)


#time ovirt-log-collector -v
DEBUG: calling(['sosreport', '--batch', '--build', '--tmp-dir=/tmp/logcollector-S4uiWg/working', '-o', 'ovirt,rpm,libvirt,general,networking,hardware,process,yum,filesys,devicemapper,selinux,kernel,apache,memory,block,java,lvm2,md,pci,processor,scsi,chrony,systemd,firewalld,openvswitch,collectd,ovirt_imageio,logs', '-k', 'rpm.rpmva=off', '-k', 'apache.log=True', '--all-logs'])

real	0m14.745s
user	0m8.921s
sys	0m1.920s




time ovirt-log-collector -v --package-manager-history
DEBUG: calling(['sosreport', '--batch', '--build', '--tmp-dir=/tmp/logcollector-oqiPVb/working', '-o', 'ovirt,rpm,libvirt,general,networking,hardware,process,yum,filesys,devicemapper,selinux,kernel,apache,memory,block,java,lvm2,md,pci,processor,scsi,chrony,systemd,firewalld,openvswitch,collectd,ovirt_imageio,logs', '-k', 'rpm.rpmva=off', '-k', 'apache.log=True', '-k', 'yum.yum-history-info=on', '--all-logs'])


real	4m9.682s
user	3m25.670s
sys	0m40.869s

Comment 6 Sandro Bonazzola 2018-01-15 07:41:19 UTC
(In reply to Douglas Schilling Landgraf from comment #5)
> PR: https://github.com/oVirt/ovirt-log-collector/pull/2


Please note that github is a backup only repo for ovirt-log-collector. Please push the patch to gerrit.ovirt.org

Comment 7 Petr Matyáš 2019-03-07 15:16:02 UTC
Verified on ovirt-log-collector-4.3.1-1.el7ev.noarch

Comment 8 Sandro Bonazzola 2019-03-13 16:37:44 UTC
This bugzilla is included in oVirt 4.3.0 release, published on February 4th 2019.

Since the problem described in this bug report should be
resolved in oVirt 4.3.0 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.


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