Bug 733736
Summary: | After reboot of one node in a cluster, if the version of cluster.conf has changed the node cannot rejoin the cluster | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Jose Castillo <jcastillo> |
Component: | cluster | Assignee: | Fabio Massimo Di Nitto <fdinitto> |
Status: | CLOSED NOTABUG | QA Contact: | Cluster QE <mspqa-list> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 6.1 | CC: | ccaulfie, cluster-maint, lhh, rpeterso, teigland |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2011-08-26 17:48:42 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: |
Description
Jose Castillo
2011-08-26 16:24:42 UTC
(In reply to comment #0) > Description of problem: > When a node in a cluster is rebooted and the running version of cluster.conf > changes, the newest version does not get transferred and the node cannot join > the cluster, or sometimes creates its own 1-node cluster. In RHEL6 this behaviour is by design. If a configuration is wrong is wrong and needs to be fixed. This is no different than expecting any other daemon on a system to fix their configuration automatically if it's wrong. In short, after lengthy discussion with Chrissie, synchronizing the configuration at startup is a very complex operation that has so many path to failures that is not worth even considering. |