Red Hat Bugzilla – Bug 1128986
[x509]Missing "--ssl-client-key-file" option in the help message of 'rhc server add/configure'
Last modified: 2016-05-25 09:20:27 EDT
Description of problem: When checking the help of command 'rhc server add/configure', found there was no --ssl-client-key-file option in the Usage example and Options list. Without --ssl-client-key-file option, adding or configuring a server which is using mutual SSL authentication and x509 certificates would fail. Version-Release number of selected component (if applicable): rhc-1.28.5.1-1.el6op.noarch How reproducible: always Steps to Reproduce: 1.rhc server add -h rhc server configure -h Actual results: Usage: rhc server-configure <server> [--hostname HOSTNAME] [--nickname NICKNAME] [--rhlogin LOGIN] [--[no-]use-authorization-tokens] [--[no-]insecure] [--use] [--skip-wizard] [--timeout SECONDS] [--ssl-ca-file FILE] [--ssl-client-cert-file FILE] [--ssl-version VERSION] Options ... --timeout SECONDS The default timeout for operations on this server --ssl-ca-file FILE An SSL certificate CA file (may contain multiple certs) to be used on this server --ssl-client-cert-file FILE An SSL x509 client certificate file to be used on this server --ssl-version VERSION The version of SSL to use to be used on this server --server SERVER Server hostname or nickname to be configured Expected results: Add this option to Usage example to Options list. Additional info:
Commit pushed to master at https://github.com/openshift/rhc https://github.com/openshift/rhc/commit/329e0f70227255ef924840d5280796b6ced85488 Bug 1128986 - Missing "--ssl-client-key-file" option in the help message of 'rhc server add/configure'
Verify this bug with rhc-1.29.3.1-1.el6op.noarch. # rhc server add -h # rhc server configure -h Options ... --ssl-ca-file FILE An SSL certificate CA file (may contain multiple certs) to be used on this server --ssl-client-cert-file An SSL x509 client certificate file to be used on this server FILE --ssl-client-key-file An RSA client certificate key FILE ...
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2014-1095.html