Bug 2107267
| Summary: | ovirt-log-collector doesn't generate database dump | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Ulhas Surse <usurse> |
| Component: | ovirt-log-collector | Assignee: | Lev Veyde <lveyde> |
| Status: | CLOSED DUPLICATE | QA Contact: | Barbora Dolezalova <bdolezal> |
| Severity: | urgent | Docs Contact: | |
| Priority: | high | ||
| Version: | 4.5.0 | CC: | bdolezal, dfodor, gdeolive, lsvaty |
| Target Milestone: | ovirt-4.5.2 | Keywords: | Regression |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | ovirt-log-collector-4.4.6 | Doc Type: | No Doc Update |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-07-28 12:13:10 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: | |||
|
Description
Ulhas Surse
2022-07-14 15:48:16 UTC
This is not a Virt bug. Not sure whether it should go to Infra or Integration, please choose appropriately. Can you please check the version of ovirt-log-collector you have on a system? The issue should not exist after ovirt-log-collector-4.4.5, so ovirt-log-collector-4.4.6 or the latest ovirt-log-collector-4.4.7 should not have this issue. (Which is basically a duplicate of BZ#2081684). bdolezal could you pls take a look? (In reply to Lev Veyde from comment #4) > The issue should not exist after ovirt-log-collector-4.4.5, so > ovirt-log-collector-4.4.6 or the latest ovirt-log-collector-4.4.7 should not > have this issue. (Which is basically a duplicate of BZ#2081684). Sorry for the late reply, it was ovirt-log-collector-4.4.5-1.el8ev.noarch when I reported the issue but now it can create dump with ovirt-log-collector-4.4.6 version. I think we can mark duplicate of 2081684 and close. *** This bug has been marked as a duplicate of bug 2081684 *** |