Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Created attachment 1508260[details]
messages and vdsm log from SPM, engine.log
Description of problem:
I run a cluster with about 15 hosts for automated testing purposes. We start to see "Data Center is being initialized" messages and disks in state "locked" or "illegal". /var/log/messages shows:
kernel: lvm[55452]: segfault at 18 ip 00007f082e700905 sp 00007ffdff4ae080 error 4 in libc-2.17.so[7f082e67e000+1c3000]
Version-Release number of selected component (if applicable):
Linux 3.10.0-862.14.4.el7.x86_64
vdsm-4.20.43-1.el7.x86_64
lvm2-2.02.177-4.el7.x86_64
oVirt 4.2.7.4-1.el7
How reproducible:
Generate load on hosts by automatically creating vms, running vm workloads, deleting vms
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
Comment 2Jonathan Earl Brassow
2019-08-07 21:18:20 UTC
Do you have the core file? That might help us get to the bottom a bit quicker.
Created attachment 1508260 [details] messages and vdsm log from SPM, engine.log Description of problem: I run a cluster with about 15 hosts for automated testing purposes. We start to see "Data Center is being initialized" messages and disks in state "locked" or "illegal". /var/log/messages shows: kernel: lvm[55452]: segfault at 18 ip 00007f082e700905 sp 00007ffdff4ae080 error 4 in libc-2.17.so[7f082e67e000+1c3000] Version-Release number of selected component (if applicable): Linux 3.10.0-862.14.4.el7.x86_64 vdsm-4.20.43-1.el7.x86_64 lvm2-2.02.177-4.el7.x86_64 oVirt 4.2.7.4-1.el7 How reproducible: Generate load on hosts by automatically creating vms, running vm workloads, deleting vms Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: