Bug 1519414
Summary: | [RFE] Handle accumulated log files rotation in /var/log/ovirt-engine/host-deploy | ||
---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Julio Entrena Perez <jentrena> |
Component: | ovirt-engine | Assignee: | Yedidyah Bar David <didi> |
Status: | CLOSED NOTABUG | QA Contact: | Liran Rotenberg <lrotenbe> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 3.6.10 | CC: | ahadas, didi, jentrena, lsurette, mavital, mkalinin, Rhev-m-bugs, rhodain, sfroemer, srevivo |
Target Milestone: | ovirt-4.3.1 | Keywords: | FutureFeature |
Target Release: | 4.3.0 | Flags: | lsvaty:
testing_plan_complete-
|
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Enhancement | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2018-12-23 07:00:20 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: | 1540201 | ||
Bug Blocks: | 1520566, 1523346 |
Description
Julio Entrena Perez
2017-11-30 17:21:57 UTC
Note that this is probably applicable for /var/log/ovirt-engine/ova as well. From the CEE point of view we time to time need older logs, but usually, we do not diagnose logs that are more than two months old. The issue is in most cases noticed earlier. I am perfectly OK with 2 months, but I would suggest adding a chapter to the documentation where we explain the behaviour and provide some information on how to adjust that if needed. Only now I realized that in 4.2 we do not have ovirt-host-mgmt logs anymore - as part of bug 1380498, we changed the code to use ansible instead of ovirt-host-mgmt (which is part of ovirt-host-deploy). Martin already noted that in bug 1540201 comment 4 but I didn't understand :-( So in 4.2 and later, logs in /var/log/ovirt-engine/host-deploy are only for actual host installations. Anyone who still has there old ovirt-host-mgmt* files can safely remove them manually. Can we close current bug, then? $ ls -l sosreport-LogCollector-20171114164426/sosreport-n433987-20171114164203/var/log/ovirt-engine/host-deploy/ | wc -l 67304 $ ls -l sosreport-LogCollector-20171114164426/sosreport-n433987-20171114164203/var/log/ovirt-engine/host-deploy/ | grep ovirt-host-mgmt | wc -l 66760 $ ls -l sosreport-LogCollector-20171114164426/sosreport-n433987-20171114164203/var/log/ovirt-engine/host-deploy/ | grep ovirt-host-mgmt | awk '{sum += $5} END {print sum}' 818166668 (780MB) $ ls -l sosreport-LogCollector-20171114164426/sosreport-n433987-20171114164203/var/log/ovirt-engine/host-deploy/ | grep -v ovirt-host-mgmt | wc -l 544 $ ls -l sosreport-LogCollector-20171114164426/sosreport-n433987-20171114164203/var/log/ovirt-engine/host-deploy/ | grep -v ovirt-host-mgmt | awk '{sum += $5} END {print sum}' 32269661 (30MB) Yes, the remaining files don't pose a problem. OK, closing as not a bug (for 4.3, it's not, anymore). In principle could have been closed as duplicate of bug 1380498, because current was fixed by the changes in that one, but not really intentionally (AFAIU). |