Bug 597258 - Update cluster.ng
Update cluster.ng
Status: CLOSED DUPLICATE of bug 520866
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: system-config-cluster (Show other bugs)
All Linux
low Severity medium
: rc
: ---
Assigned To: Ryan McCabe
Cluster QE
Depends On: 597253
  Show dependency treegraph
Reported: 2010-05-28 10:11 EDT by Marek Grac
Modified: 2010-08-09 12:00 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 597253
Last Closed: 2010-08-09 12:00:45 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Marek Grac 2010-05-28 10:11:53 EDT
In RHEL5 there will be probably same issue also with

login_timeout, shell_timeout, power_timeout

(list of all options is available in fence-agents lib/fencing.py)

+++ This bug was initially created as a clone of Bug #597253 +++

You wrote:
> While the actual fix appears to work fine, there is a problem with
validating the cluster.conf with the newly added power_wait atttibute:

Indeed, the schema used in validation is part of the system-config-cluster
package which was not refreshed as part of the hotfix. To have it recognise
the new attribute, it would need a patch similar to the following:

--- ./src/misc/cluster.ng.orig 2010-03-10 16:02:40.899864461 +0100
+++ ./src/misc/cluster.ng 2010-03-10 16:08:29.717864438 +0100
@@ -98,6 +98,9 @@
          <attribute name="force"/>
+        <optional>
+         <attribute name="power_wait"/>
+        </optional>
        <!-- GNBD -->
Comment 1 Lon Hohberger 2010-08-09 12:00:45 EDT

*** This bug has been marked as a duplicate of bug 520866 ***

Note You need to log in before you can comment on or make changes to this bug.