| Summary: | ccs_tool doesn't recognize the --no_ccs option with 'addfence' commands | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 5 | Reporter: | Alan Staples <alan.staples> |
| Component: | cman | Assignee: | Lon Hohberger <lhh> |
| Status: | CLOSED WONTFIX | QA Contact: | Cluster QE <mspqa-list> |
| Severity: | low | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 5.5 | CC: | cluster-maint, edamato |
| 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: | 2012-02-10 18:14:45 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
Development Management has reviewed and declined this request. You may appeal this decision by reopening this request. |
Description of problem: The ccs_tool utility does not recognize the "--no_ccs" option in conjunction with "addfence" commands. It reports "addfence: unrecognized option `--no_ccs'" and displays usage information, which includes reference to the "--no_ccs" option. Additionally, the exit value is '0', so if I script the use of this utility, I cannot rely on the exit value to determine whether the command executed successfully. Version-Release number of selected component (if applicable): cman-2.0.115-34.el5 How reproducible: Always Steps to Reproduce: 1. Attempt to create a new fence device, e.g. ccs_tool addfence --no_ccs dummy_device manual nodename=dummy Actual results: Instead of adding the fence device, the following is displayed: addfence: unrecognized option `--no_ccs' Usage: ccs_tool addfence [options] <name> <agent> [param=value] -c --configfile Name of configuration file (/etc/cluster/cluster.conf) -o --outputfile Name of output file (defaults to same as --configfile) -C --no_ccs Don't tell CCSD about this change default: run "ccs_tool update" if file is updated in place) -F --force_ccs Force "ccs_tool upgrade" even if input & output files differ -h --help Display this help text Expected results: The /etc/cluster/cluster.conf file is updated successfully, but 'ccs_tool update' is not automatically called after the modicification. If I use "-C" instead of "--no_ccs" the tool acts as expected. Additional info: