Bug 733424

Summary: Relax-NG errors reported after cman_tool join; cman_tool leave is interrupted
Product: Red Hat Enterprise Linux 6 Reporter: Jaroslav Kortus <jkortus>
Component: clusterAssignee: Fabio Massimo Di Nitto <fdinitto>
Status: CLOSED ERRATA QA Contact: Cluster QE <mspqa-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.2CC: ccaulfie, cluster-maint, lhh, rpeterso, teigland
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: cluster-3.0.12.1-18.el6 Doc Type: Bug Fix
Doc Text:
Do not document.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2011-12-06 14:53:11 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
corrupted /var/lib/cluster none

Description Jaroslav Kortus 2011-08-25 16:51:30 UTC 
Description of problem:
# cman_tool join
Relax-NG parser error : Reference SERVICE has no matching definition

Version-Release number of selected component (if applicable):
cman-3.0.12.1-14.el6.x86_64

How reproducible:
sometimes

Steps to Reproduce (cluster-wide):
1. run while true; do cman_tool join; cman_tool leave; done
2. feel lucky
3. hit ctrl-c couple of times
  
Actual results:
it may happen that the regenerated schema gets corrupted and cluster operations on that node are disabled until the error is resolved.

Expected results:
one of:
* nothing like corruption happening
* message telling users about ccs_update_schema
* removing the cache automatically

Additional info:
Comment 5 Jaroslav Kortus 2011-08-26 09:39:48 UTC 
Created attachment 520048 [details]
corrupted /var/lib/cluster
Comment 9 Fabio Massimo Di Nitto 2011-09-03 09:20:50 UTC 
http://git.fedorahosted.org/git/?p=cluster.git;a=commitdiff;h=e236677a5c238673a94923c34dcd4f83f4c9374b

The fix simply invalidates the ccs_update_schema cache if any trap is received, forcing a schema regeneration in the next run.

I am unable to reproduce the issue reported after applying this patch.

Jaroslav, I left the manually patched version of ccs_update_schema on the marathon cluster (all 5 nodes), for you to stress some more, and should be able to provide a build by Monday.
Comment 10 Jaroslav Kortus 2011-09-05 11:51:22 UTC 
Works well with the patched version, I'm not able to reproduce it any more.

The easiest way how to reproduce this is start the cman_join cman_leave loop on all nodes and kill -9 corosync on one, wait for messages like "cman_tool: Error leaving cluster: Operation already in progress" appearing rapidly and then try to stop the loop (ctrl-c, ctrl-q). Eventually it won't be able to start again.

Thanks Fabio, I'll wait for an official build.
Comment 11 Jaroslav Kortus 2011-09-12 13:44:01 UTC 
can't reproduce it in any longer with cman-3.0.12.1-19.el6.x86_64
Comment 12 Lon Hohberger 2011-10-26 22:36:22 UTC 
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
Do not document.
Comment 13 errata-xmlrpc 2011-12-06 14:53:11 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2011-1516.html