Bug 218815
| Summary: | Conga creates cluster.conf files w/o enforcing the definition of a fencing device | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 5 | Reporter: | Len DiMaggio <ldimaggi> |
| Component: | conga | Assignee: | Jim Parsons <jparsons> |
| Status: | CLOSED NOTABUG | QA Contact: | Corey Marthaler <cmarthal> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 5.0 | CC: | cluster-maint, djansa, jlaska, kanderso, kupcevic, rmccabe |
| 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-12-12 16:41:16 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: | |||
RHEL5 GA requirement = Cluster configuration with Luci, CGA-0200 - Creating a cluster (http://intranet.corp.redhat.com/ic/intranet/RHEL500ReleaseCriteria#Conga) Impact statement - the user must modify the cluster config - post creation - and add the fencing device information for the cluster and each cluster node. Jim: this was always allowed. |
Description of problem: Conga creates cluster.conf files w/o enforcing the definition of a fencing device - the user is able to modify the file after it's creation, but by default, the user is not required to define a fencing device Version-Release number of selected component (if applicable): luci-0.8-25.el5 ricci-0.8-25.el5 How reproducible: 100% Steps to Reproduce: 1. Create a new cluster via Conga 2. When the nodes are rebooted, the cman service starts on all the nodes, then tries to fence some members, this fails (in a 3-node cluster, it fails on one node) - that node is blocked Actual results: The user has to modify the cluster.conf file - this can be done via Conga - to reference a fencing device. Expected results: The user should be required to specify a fencing device - so that when a cluster is created in Conga, it comes up and is fully functional by default. Additional info: Here's an example cluster.conf file as generated by Conga: ------------------------------------------------ <?xml version="1.0"?> <cluster alias="testCluster" config_version="1" name="testCluster"> <fence_daemon post_fail_delay="0" post_join_delay="3"/> <clusternodes> <clusternode name="tng3-2.lab.msp.redhat.com" nodeid="1" votes="1"/> <clusternode name="tng3-3.lab.msp.redhat.com" nodeid="2" votes="1"/> <clusternode name="tng3-4.lab.msp.redhat.com" nodeid="3" votes="1"/> </clusternodes> <cman/> <fencedevices/> <rm/> </cluster> ------------------------------------------------