Bug 502012
| Summary: | cluster.ng secure tag | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 5 | Reporter: | Ervin Horvath <ervin.horvath> |
| Component: | system-config-cluster | Assignee: | Ryan McCabe <rmccabe> |
| Status: | CLOSED DUPLICATE | QA Contact: | Cluster QE <mspqa-list> |
| Severity: | medium | Docs Contact: | |
| Priority: | low | ||
| Version: | 5.3 | CC: | bbrock, cluster-maint |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2010-07-01 19:07:36 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: | |||
*** This bug has been marked as a duplicate of bug 606826 *** |
Description of problem: cluster.ng schema validator does not accept the new secure=<param> key in fence_bladecenter tag Version-Release number of selected component (if applicable): How reproducible: yes Steps to Reproduce: 1.have a basic cluster.conf file with fencedevice name="blade_fence" agent="fence_bladecenter" ipaddr="1.2.3.4" login="login" passwd="pwd"/ and check it against the schema validator with 2.xmllint --noout --relaxng /usr/share/system-config-cluster/misc/cluster.ng /tmp/basic.conf and it says it is valid 3. no edit the config file, and add the the ssh-forcing tag mentioned in the manpage of fence_bladecenter -x on command line OR "secure = < param > Use secure connection over ssh." in xml so it looks sg. like this: fencedevice name="blade_fence" agent="fence_bladecenter" ipaddr="1.2.3.4" login="login" passwd="pwd" secure="1"/ 4. rerun the step2 validation, and it fails Actual results: Relax-NG validity error : Extra element fencedevices in interleave Expected results: validates Additional info: probably the cluster.conf is good, only cluster.ng is not up to date in rhel5.3