Bug 1397923
Summary: | [RHGS + Ganesha] : Corosync crashes and dumps core when glusterd/nfs-ganesha are restarted amidst continous I/O | |||
---|---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Ambarish <asoman> | |
Component: | corosync | Assignee: | Jan Friesse <jfriesse> | |
Status: | CLOSED DEFERRED | QA Contact: | cluster-qe <cluster-qe> | |
Severity: | high | Docs Contact: | ||
Priority: | unspecified | |||
Version: | 7.3 | CC: | amukherj, asoman, bturner, ccaulfie, cluster-maint, jthottan, kkeithle, rhinduja, skoduri | |
Target Milestone: | rc | |||
Target Release: | --- | |||
Hardware: | x86_64 | |||
OS: | Linux | |||
Whiteboard: | ||||
Fixed In Version: | Doc Type: | If docs needed, set a value | ||
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 1402308 (view as bug list) | Environment: | ||
Last Closed: | 2017-01-16 12:04:05 UTC | Type: | Bug | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: | ||||
Bug Depends On: | ||||
Bug Blocks: | 1402308, 1402344 |
Description
Ambarish
2016-11-23 14:59:39 UTC
@Ambarish: This assertion usually happens ether when: - ifdown happens - there is more than one cluster with same configuration on the network - different encryption methods For this BZ, ifdown looks like a case. "[22660] gqas009.sbu.lab.eng.bos.redhat.com corosyncnotice [TOTEM ] The network interface is down." in gqas009/corosync.log. Please never do ifdown. Ifdown makes corosync break. If you are using NM (recommended in RHEL 7), install NetworkManager-config-server. Can you please retest without ifdown? Jan, Thanks for your comment. But I didn't do an ifdown explicitly.Not really sure what triggered it?I just restarted gluster and ganesha daemons while pumping IO from my mounts,when one of my servers bounced. Also,you mentioned about corosync breaking on ifdowns.Is it a known issue?Can you please point me to a BZ? Corosync + ifdown is long term issue. It's very hard to fix and we plan solution for corosync 3.x (so RHEL.next), so fix is probably not going to happen in RHEL 7/6. I don't really know what is main reason for ifdown but it for sure happened (as noted please see "The network interface is down" in logs). Make sure to install NetworkManager-config-server if you are using NM. Please try to retest if bug happens again even when "The network interface is down" is not in corosync.log. *** Bug 1402344 has been marked as a duplicate of this bug. *** The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days |