Bug 1426677

Description of problem:
When adding new master(s) to existing cluster with scaleup playbook, it doesn't consider custom ca certificate specified in openshift_master_overwrite_certificates. This causes failed to complete the scaleup playbook. It means we can't add new master(s) when we use custom ca cert.

Version-Release number of selected component (if applicable):
# openshift version
openshift v3.4.1.7

# ansible version --version
ansible 2.2.0.0
  config file = /etc/ansible/ansible.cfg
  configured module search path = Default w/o overrides

How reproducible:
I reproduced on my environment.

Steps to Reproduce:
1. Create custom ca cert and web server cert and key for custom certificates.

2. Set up multi-masters OpenShift cluster with specifying openshift_master_overwrite_certificates like below.
```
openshift_master_named_certificates=[{"certfile": "/root/www.crt", "keyfile": "/root/www.key", "cafile": "/root/cacert.pem", "names": ["lb.example.com"]}]
openshift_master_overwrite_named_certificates=true
```

3. At this point, OpenShift master API and web console are secured with specified certificate and custom CA.

4. Add new node with scaleup playbook. I added new_master and new_nodes in ansible host file like below. "openshift_master_named_certificates" and "openshift_master_overwrite_named_certificates" remain the same as above.

```
[OSEv3:children]
masters
nodes
etcd
lb
new_masters
new_nodes

[new_nodes]
new-master.example.com penshift_node_labels="{'region': 'infra', 'zone': 'default'}" openshift_schedulable=false

[new_masters]
new-master.example.com
```

Actual results:
Playbook failed by below error.
```
TASK [openshift_master : Wait for API to become available] *********************
FAILED - RETRYING: TASK: openshift_master : Wait for API to become available (120 retries left).
FAILED - RETRYING: TASK: openshift_master : Wait for API to become available (119 retries left).
** snipping **
fatal: [new-master.example.com]: FAILED! => {
    "attempts": 120, 
    "changed": false, 
    "cmd": [
        "curl", 
        "--silent", 
        "--tlsv1.2", 
        "--cacert", 
        "/etc/origin/master/ca-bundle.crt", 
        "https://lb.example.com:8443/healthz/ready"
    ], 
    "delta": "0:00:00.149118", 
    "end": "2017-02-24 02:55:38.146070", 
    "failed": true, 
    "rc": 60, 
    "start": "2017-02-24 02:55:37.996952", 
    "warnings": []
}
```

On the new master:
```
# curl --tlsv1.2 --cacert /etc/origin/master/ca-bundle.crt https://lb.example.com:8443/healthz/readycat /etc/origin/master/ca-bundle.crt
curl: (60) Peer's Certificate issuer is not recognized.
More details here: http://curl.haxx.se/docs/sslcerts.html

curl performs SSL certificate verification by default, using a "bundle"
 of Certificate Authority (CA) public keys (CA certs). If the default
 bundle file isn't adequate, you can specify an alternate file
 using the --cacert option.
If this HTTPS server uses a certificate signed by a CA represented in
 the bundle, the certificate verification probably failed due to a
 problem with the certificate (it might be expired, or the name might
 not match the domain name in the URL).
If you'd like to turn off curl's verification of the certificate, use
 the -k (or --insecure) option.
curl: (3) <url> malformed
```

Expected results:
Complete the playbook and new master is successfully added.

Additional info:
The customer is facing this issue and can't add new master at present. I attached the case info at the next private comment.