Bug 1360621
| Summary: | log-collector should collect detailed yum/dnf history | ||
|---|---|---|---|
| Product: | [oVirt] ovirt-log-collector | Reporter: | Yedidyah Bar David <didi> |
| Component: | SOS-plugins | Assignee: | Douglas Schilling Landgraf <dougsland> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Petr Matyáš <pmatyas> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 4.0.0 | CC: | bugs, didi, dougsland, lsvaty, lveyde, pmatyas |
| Target Milestone: | ovirt-4.3.0 | Keywords: | Improvement |
| Target Release: | 4.3.0 | Flags: | rule-engine:
ovirt-4.3+
dnecpal: testing_plan_complete- ylavi: planning_ack+ sbonazzo: devel_ack+ pstehlik: testing_ack+ |
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | ovirt-log-collector-4.3.0_beta1 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-03-13 16:37:44 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | Integration | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1360623, 1360624 | ||
| Bug Blocks: | |||
|
Description
Yedidyah Bar David
2016-07-27 07:38:23 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. (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. Lev, dependent bugs on sos are closed, can you check if we can move on with this bug? (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. 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 (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 Verified on ovirt-log-collector-4.3.1-1.el7ev.noarch 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. |