| Summary: | yum / yum-complete-transaction sometimes hang / dumps '/usr/bin/python: double free or corruption' message | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Frantisek Reznicek <freznice> |
| Component: | rpm | Assignee: | Panu Matilainen <pmatilai> |
| Status: | CLOSED NOTABUG | QA Contact: | BaseOS QE Security Team <qe-baseos-security> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.2 | CC: | esammons, pknirsch |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-03-08 12:36:39 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Frantisek Reznicek
2012-01-10 15:22:43 UTC
This reminds me strongly of a kernel bug we had in RHEL-6 Beta where Transparent Hugetables were corrupting the guest memory in very rare cases (which got triggered by rpm and bdb). Are you running the latest 6.2 updates on the host and guest systems? Thanks & regards, Phil I'm going to retest to see if it is still happening. At the time of report guests were (getting) updated. Virtualization host is not RHEL (F8 with custom virtualization:) kvm-65-15.fc8.x86_64 libvirt-0.6.1-1.fc8.x86_64 libvirt-devel-0.6.1-1.fc8.x86_64 libvirt-python-0.6.1-1.fc8.x86_64 python-virtinst-0.400.3-3.fc9.noarch qemu-0.9.1-6.fc8.x86_64 qemu-img-0.9.1-6.fc8.x86_64 virt-manager-0.7.0-8.fc8.x86_64 virt-manager-debuginfo-0.7.0-8.fc8.x86_64 virt-viewer-0.0.3-1.fc8.x86_64 I reproduced the issue again on updated rhel6.2 guest (x86_64). I'm not seeing this behavior with RHEL's virtualization (kvm-*83-239.el5 libvirt-*0.8.2-22.el5) I'm going to confirm by building them on f8. The issue is indeed caused by virtualization host kvm issues. When switched to kvm-74 issue gone away which correlates with fact that this behavior was never detected on rhel6 guests virtualized on RHEL5.x virt. hosts. Issue has no content. -> CLOSED / NOT-A-BUG Ok. Thanks for confirming it was indeed a virtualization bug, rpm/bdb seems to be quite a sucker for those. |