Bug 172295 - clean_start should NOT be set to '1' for two-node clusters
Summary: clean_start should NOT be set to '1' for two-node clusters
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Cluster Suite
Classification: Retired
Component: redhat-config-cluster
Version: 4
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jim Parsons
QA Contact: Cluster QE
URL:
Whiteboard:
Depends On:
Blocks: 164914
TreeView+ depends on / blocked
 
Reported: 2005-11-02 14:51 UTC by Jim Parsons
Modified: 2009-04-16 20:10 UTC (History)
1 user (show)

Fixed In Version: RHBA-2006-0198
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-03-09 19:50:44 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2006:0198 0 normal SHIPPED_LIVE system-config-cluster bug fix update 2006-03-09 05:00:00 UTC

Description Jim Parsons 2005-11-02 14:51:30 UTC 
Description of problem:
The fence_daemon params that are written out by default always set clean_start
to '1'. This should NOT be the case for two-node clusters


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 3 Jim Parsons 2005-11-09 18:15:32 UTC 
Actually, according to DCT, this should be removed entirely from the UI and not
set by default to any value -- not just for the two node case.
Comment 4 Jim Parsons 2005-11-09 18:30:47 UTC 
Fixed in 1.0.17-1.0
Comment 6 Red Hat Bugzilla 2006-03-09 19:50:44 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-0198.html
Note You need to log in before you can comment on or make changes to this bug.