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.
Description of problem: During ha-lvm tests, following error occured: [rgmanager] [ha_lvm_setup] Starting ricci on all nodes [rgmanager] [ha_lvm_setup] Starting ricci on all nodes [rgmanager] [ha_lvm_setup] Starting ricci on all nodes [rgmanager] [ha_lvm_setup] Copying cluster conf file [rgmanager] [ha_lvm_setup] Updating cman version [rgmanager] [ha_lvm_setup] cman_tool: cannot get COROSYNC_DEFAULT_CONFIG_IFACE [rgmanager] [ha_lvm_setup] couldn't cman_tool version on marathon-01 Looking at the logs, there was corosync aborted with sig 11: Core was generated by `corosync -f'. Program terminated with signal 11, Segmentation fault. #0 sem_wait () at ../nptl/sysdeps/unix/sysv/linux/x86_64/sem_wait.S:45 45 movl (%rdi), %eax (gdb) bt full #0 sem_wait () at ../nptl/sysdeps/unix/sysv/linux/x86_64/sem_wait.S:45 No locals. #1 0x00000038d4a02998 in ipc_sem_wait (conn=0x20c9460) at ../include/corosync/coroipc_ipc.h:198 sem = 0x10 fd = 0 res = <value optimized out> #2 pthread_ipc_consumer (conn=0x20c9460) at coroipcs.c:673 conn_info = 0x20c9460 header = <value optimized out> coroipc_response_header = {size = 0, id = 0, error = 0} send_ok = <value optimized out> new_message = <value optimized out> sem_value = 0 #3 0x00000038d32077e1 in start_thread (arg=0x7fed2c093450) at pthread_create.c:301 __res = <value optimized out> pd = 0x7fed2c093450 now = <value optimized out> unwind_buf = {cancel_jmp_buf = {{jmp_buf = {140656622777424, -4930327191805661111, 34378872, 140656622778128, 0, 3, 4920654939882614857, -4908268514975322039}, mask_was_saved = 0}}, priv = {pad = {0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0, canceltype = 0}}} not_first_call = <value optimized out> pagesize_m1 = <value optimized out> sp = <value optimized out> freesize = <value optimized out> #4 0x00000038d2ee153d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115 No locals. Version-Release number of selected component (if applicable): corosync-1.2.3-21.el6.x86_64 How reproducible: not sure Steps to Reproduce: 1. run ha-lvm sts tests 2. 3. Actual results: corosync core Expected results: no core Additional info: