Bug 144945
Summary: | ccsd not recognizing that gulm is quorate when quorum is lost and then restablished | ||||||
---|---|---|---|---|---|---|---|
Product: | [Retired] Red Hat Cluster Suite | Reporter: | Adam "mantis" Manthei <amanthei> | ||||
Component: | magma-plugins | Assignee: | Lon Hohberger <lhh> | ||||
Status: | CLOSED CURRENTRELEASE | QA Contact: | Cluster QE <mspqa-list> | ||||
Severity: | high | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | 4 | CC: | cluster-maint | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | All | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | RHCS4U1 | Doc Type: | Bug Fix | ||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2005-11-22 18:24:13 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-01-12 22:02:46 UTC
ccs uses magma to get cluster events. If magma is not telling CCS that quorum has been reestablished, there is nothing ccs can do about it. Could be gulm magma plugin not pushing the state change back up to the parent; will check this out. I did a fudge where I had 2 of 3 masters online and listened with my magma event listener: On node "red": [root@red cluster]# lock_gulmd --servers "red green blue" --cluster_name foo [root@red cluster]# cpt listen ... On node "green": [root@green gulm]# lock_gulmd --servers "red green blue" --cluster_name foo [root@green gulm]# gulm_tool shutdown localhost:core [root@green gulm]# lock_gulmd --servers "red green blue" --cluster_name foo Output of 'cpt' on red: Connected via: GuLM Plugin v1.0 Listening for events (group cluster::usrm)... +++ Dump of 0x8c22020 (1 nodes) red.lab.boston.redhat.com (id 0xffff0000284fa8c0) state Up - red.lab.boston.redhat.com 192.168.79.40 --- Done === Waiting for events. *E* Quorum formed *E* Quorum dissolved *E* Quorum formed The form/dissolve/form correspond to lock_gulmd master being started on green. It looks like libgulm doesn't detect when lg_lock_logout is called and lock_gulmd is no longer running. However, given that once we get CE_SHUTDOWN, the application must exit without calling locks, etc., it's quite easy to fix this in the gulm magma plugin. Created attachment 109734 [details]
patch which changes gulm.so to kill lock FD on shutdown
|