Bug 1203435
| Summary: | The '--ssl-client-key-file' option does not write to servers.yml | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Brenton Leanhardt <bleanhar> |
| Component: | oc | Assignee: | Miciah Dashiel Butler Masters <mmasters> |
| Status: | CLOSED ERRATA | QA Contact: | libra bugs <libra-bugs> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 2.2.0 | CC: | adellape, ffranz, gpei, jokerman, libra-bugs, libra-onpremise-devel, mmccomas, pruan, tiwillia, xiuwang |
| Target Milestone: | --- | Keywords: | Upstream |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | rhc-1.35.1.1-1 | Doc Type: | Bug Fix |
| Doc Text: |
Previously when running the "rhc setup" command with the "--ssl-client-key-file" option, the configuration for the SSL client key file was not written to the ~/.openshift/servers.yml file. Additionally, while using the "rhc server add" command with the "--ssl-client-key-file" option successfully wrote the key file to the servers.yml file, the output for the "rhc server list" command did not list the key file information. This bug fix updates the client tools to ensure the key file configuration is written and listed in these scenarios, and as a result adding key files with the client tools now works as expected.
|
Story Points: | --- |
| Clone Of: | 1187812 | Environment: | |
| Last Closed: | 2015-04-06 17:06:53 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1187812 | ||
| Bug Blocks: | |||
|
Description
Brenton Leanhardt
2015-03-18 19:59:53 UTC
Verify this bug with rhc 1.35.1.1
1. When using 'rhc setup' with the ssl client key options, related configuration would be saving to /root/.openshift/express.conf, list clearly when running 'rhc server list'
[root@broker ~]# rhc setup -l gpei --ssl-client-cert-file /root/gpei.crt --ssl-client-key-file /root/gpei.key --ssl_ca_file /root/ca.crt
...
Saving configuration to /root/.openshift/express.conf ... done
[root@broker ~]# cat /root/.openshift/express.conf |grep -v '^#'|sort
default_rhlogin=gpei
insecure=false
libra_server=broker.ose22-manual.com.cn
ssl_ca_file=/root/ca.crt
ssl_client_cert_file=/root/gpei.crt
ssl_client_key_file=/root/gpei.key
use_authorization_tokens=true
[root@broker ~]# rhc server list
Server 'server1' (in use)
-------------------------
Hostname: broker.ose22-manual.com.cn
Login: gpei
Use Auth Tokens: true
Insecure: false
SSL x509 Client Cert File: /root/gpei.crt
SSL x509 Client Key File: /root/gpei.key
SSL Cert CA File: /root/ca.crt
2. When using ‘server add’ to setup the configuration of a server with '--ssl-client-key-file' option, the key configuration could be written into server.yml, and could be list using 'server list'.
[root@broker ~]# rhc server add broker.ose22-manual.com.cn ose --ssl-client-cert-file /root/gpei.crt --ssl-client-key-file /root/gpei.key --ssl-ca-file /root/ca.crt
...
Saving server configuration to /root/.openshift/servers.yml ... done
[root@broker .openshift]# cat servers.yml
---
- server:
login: gpei
ssl_ca_file: /root/ca.crt
hostname: broker.ose22-manual.com.cn
nickname: ose
ssl_client_key_file: /root/gpei.key
ssl_client_cert_file: /root/gpei.crt
use_authorization_tokens: true
insecure: false
[root@broker .openshift]# rhc server list
Server 'ose' (in use)
---------------------
Hostname: broker.ose22-manual.com.cn
Login: gpei
Use Auth Tokens: true
Insecure: false
SSL x509 Client Cert File: /root/gpei.crt
SSL x509 Client Key File: /root/gpei.key
SSL Cert CA File: /root/ca.crt
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. https://rhn.redhat.com/errata/RHBA-2015-0779.html |