Bug 148016
Summary: | "if a node is kicked out of the cluster things go ape-shit" | ||||||
---|---|---|---|---|---|---|---|
Product: | [Retired] Red Hat Cluster Suite | Reporter: | Adam "mantis" Manthei <amanthei> | ||||
Component: | dlm | Assignee: | David Teigland <teigland> | ||||
Status: | CLOSED DUPLICATE | QA Contact: | Cluster QE <mspqa-list> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | 4 | CC: | cluster-maint | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | All | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2006-02-21 19:08: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
Adam "mantis" Manthei
2005-02-14 20:14:40 UTC
Created attachment 111066 [details]
logs and console from crashed cluster
Assigned to Dave in the first instance, because the first death is in gfs-kernel/dlm/lock.c - though I suspect this bug may bounce around a bit before being closed. trin-05 is where the assertion failed and it's evident from its log file that the cluster was shut down, which causes the lockspaces to be shut down, which causes the assertion failure. Same problem we've seen before. (In reply to comment #3) > trin-05 is where the assertion failed and it's evident from its > log file that the cluster was shut down, which causes the lockspaces > to be shut down, which causes the assertion failure. Same problem > we've seen before. I didn't shut down the cluster. Does the cluster for some reason shut itself down? If so why and when? The leaving the cluster is probably bug #139738. This bug addresses the seperate issue that Patrick referred to in bug #139738 comment #10 where "all hell breaks loose" Patrick had this to say as well: This bug is not the same as bug #139738 even though it is (in most circumstances) caused by it. There are potentially other causes of this error. So, even if we close bug #139738 this bug is not fixed. The problem is that /if/ cman gets kicked out of the cluster then these errors occur. bug #139738 is the fact that cman /does/ get kicked out of the cluster. The reason I wanted a seperate bug opened for this problem is so that it doesn't get lost when bug #139738 goes away. It's likely that such (inadvisable) commands such as "cman_tool kill" or "cman_tool leave force" would also cause these errors. This belongs in a new bz. *** This bug has been marked as a duplicate of 148788 *** Changed to 'CLOSED' state since 'RESOLVED' has been deprecated. |