Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 677998

Summary: fence_ilo power_wait option not recognized by ccs_config_validate
Product: Red Hat Enterprise Linux 6 Reporter: Gianluca Cecchi <gianluca.cecchi>
Component: clusterAssignee: Fabio Massimo Di Nitto <fdinitto>
Status: CLOSED DUPLICATE QA Contact: Cluster QE <mspqa-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.0CC: ccaulfie, cluster-maint, lhh, rpeterso, teigland
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-02-16 14:13:58 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 Gianluca Cecchi 2011-02-16 13:17:02 UTC
Description of problem:
trying to put power_wait option in my cluster.conf


Version-Release number of selected component (if applicable):
cman-3.0.12-23.el6_0.4.x86_64

How reproducible:
always

Steps to Reproduce:
1. this line
<fencedevice agent="fence_ilo" ipaddr="10.4.192.212" login="fenceuser" name="ilonode01" passwd_script="/usr/local/bin/pwd_ilonode01.sh"/>

[root@rhev1 cluster]# ccs_config_validate
Configuration validates


2. change into
<fencedevice agent="fence_ilo" ipaddr="10.4.192.212" login="fenceuser" name="ilonode01" passwd_script="/usr/local/bin/pwd_ilonode01.sh" power_wait="5"/>



3. run 
[root@rhev1 cluster]# ccs_config_validate
  
Actual results:

Relax-NG validity error : Extra element fencedevices in interleave
tempfile:20: element fencedevices: Relax-NG validity error : Element cluster failed to validate content
tempfile:15: element device: validity error : IDREF attribute name references an unknown ID "ilonode02"
Configuration fails to validate

Expected results:

Configuration validates

Additional info:

It seems power_wait should be ok in /usr/sbin/fence_ilo.....
I have
fence-agents-3.0.12-8.el6_0.2.x86_64
and there is inside it:
def main():
        device_opt = [  "help", "version", "agent", "quiet", "verbose", "debug",
                        "action", "ipaddr", "login", "passwd", "passwd_script",
                        "ssl", "ribcl", "inet4_only", "inet6_only", "ipport",
                        "power_timeout", "shell_timeout", "login_timeout", "power_wait" ]

Comment 2 Fabio Massimo Di Nitto 2011-02-16 14:13:58 UTC
This issue has already been addressed. Thanks for your report.

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