Bug 193905

Summary: CCS will grab random conf file from network if one is not present locally
Product: [Retired] Red Hat Cluster Suite Reporter: Jonathan Earl Brassow <jbrassow>
Component: ccsAssignee: Jonathan Earl Brassow <jbrassow>
Status: CLOSED ERRATA QA Contact: Cluster QE <mspqa-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 4CC: cluster-maint, cmarthal
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: RHBA-2006-0554 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-08-10 21:16: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:

Description Jonathan Earl Brassow 2006-06-02 20:01:01 UTC 
/*
     * no cluster.conf file.
     * We used to simply return 0 here and go fetch a random
     * conf file from the network.  This worked well in environments
     * that had only one cluster in broadcast range, but it has
     * caused to much confusion when there is more than one cluster.
     * Additionally, our docs and manuals tell users to copy the
     * file to each node anyway.
     *
     * In the event that there is a cluster.conf file, ccs will
     * still ensure that it has the most up-to-date copy of the
     * file in relation to the other nodes in the quorate cluster.
     */
Comment 3 Red Hat Bugzilla 2006-08-10 21:16:12 UTC 
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2006-0554.html