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.
Bug 587526 - ccs_sync SIGABRTs when called with non-existing cluster node
Summary: ccs_sync SIGABRTs when called with non-existing cluster node
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: ricci
Version: 6.0
Hardware: x86_64
OS: Linux
low
low
Target Milestone: rc
: ---
Assignee: Chris Feist
QA Contact: Cluster QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-04-30 07:08 UTC by Ingvar Hagelund
Modified: 2016-04-26 14:43 UTC (History)
2 users (show)

Fixed In Version: ricci-0.16.2-6.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-15 14:44:13 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Patch to fix bz (633 bytes, patch)
2010-05-18 22:01 UTC, Chris Feist
no flags Details | Diff

Description Ingvar Hagelund 2010-04-30 07:08:14 UTC
Description of problem:
If ccs_sync is called with wrong parameters, it dies screeming with SIGABRT and dumps core.

Version-Release number of selected component (if applicable):
0.16.2-2

How reproducible:
Allways

Steps to Reproduce:
1. run a bogus ccs_sync command, like "ccs_sync foo"
2. There is no cluster node "foo". See the process die screaming
  

Actual results:

Warning: foo is not listed as a node in /etc/cluster/cluster.conf
*** glibc detected *** ccs_sync: double free or corruption (top): 0x0000000001039710 ***
======= Backtrace: =========
/lib64/libc.so.6[0x3c07274ab6]
ccs_sync[0x4020ea]
/lib64/libc.so.6(__libc_start_main+0xfd)[0x3c0721eb1d]
ccs_sync[0x401ab9]
======= Memory map: ========
(...snip...)
Aborted (core dumped)

Expected results:

Should just echo the error message and die with no further noise.

Additional info:
have only tested on x86_64

Comment 2 RHEL Program Management 2010-04-30 08:45:24 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.

Comment 3 Chris Feist 2010-05-18 22:01:08 UTC
Fixed segfault:

Test output:

[root@ask-03 ~]# ccs_sync blah
Error: blah is not listed as a node in /etc/cluster/cluster.conf
[root@ask-03 ~]#

Comment 4 Chris Feist 2010-05-18 22:01:40 UTC
Created attachment 414975 [details]
Patch to fix bz

Comment 8 releng-rhel@redhat.com 2010-11-15 14:44:13 UTC
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.


Note You need to log in before you can comment on or make changes to this bug.