Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1650384

Summary: Ansible installer fails to generate custom certificates for the registry during the "Hosted Install" phase.
Product: OpenShift Container Platform Reporter: Mitchell Rollinson <mirollin>
Component: InstallerAssignee: Patrick Dillon <padillon>
Installer sub component: openshift-ansible QA Contact: Gaoyun Pei <gpei>
Status: CLOSED DUPLICATE Docs Contact:
Severity: medium    
Priority: medium CC: kborup, mirollin
Version: 3.11.0   
Target Milestone: ---   
Target Release: 3.11.z   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-03-14 20:36:13 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:

Comment 1 Mitchell Rollinson 2018-11-16 04:20:27 UTC 
Version-Release number of the following components:
3.11

[rpm -q openshift-ansible]

openshift-ansible-3.11.16-1.git.0.4ac6f81.el7.noarch        Fri Oct 19 09:33:41 2018
openshift-ansible-docs-3.11.16-1.git.0.4ac6f81.el7.noarch   Fri Oct 19 09:33:40 2018
openshift-ansible-playbooks-3.11.16-1.git.0.4ac6f81.el7.noarch Fri Oct 19 09:33:37 2018
openshift-ansible-roles-3.11.16-1.git.0.4ac6f81.el7.noarch  Fri Oct 19 09:33:09 2018

[rpm -q ansible] 

ansible-2.6.5-1.el7ae.noarch                                Fri Oct 19 09:32:58 2018
openshift-ansible-3.11.16-1.git.0.4ac6f81.el7.noarch        Fri Oct 19 09:33:41 2018
openshift-ansible-docs-3.11.16-1.git.0.4ac6f81.el7.noarch   Fri Oct 19 09:33:40 2018
openshift-ansible-playbooks-3.11.16-1.git.0.4ac6f81.el7.noarch Fri Oct 19 09:33:37 2018
openshift-ansible-roles-3.11.16-1.git.0.4ac6f81.el7.noarch  Fri Oct 19 09:33:09 2018

ansible --version

ansible 2.6.5
Comment 4 Scott Dodson 2018-11-26 20:21:01 UTC 
Can you clarify what you mean when you mention the workaround? Are you saying that you did that and the registry deployed successfully thereafter?

Also, can you clarify what action was taken that replaced /etc/origin/master/ca.crt with /etc/origin/master/named_certificates/ca.crt ? That shouldn't have happened.
Comment 7 Mitchell Rollinson 2018-12-13 20:17:44 UTC 
Good day,

May i have a case update for the cu please.

Thanks

Mitch
Comment 8 Mitchell Rollinson 2019-01-07 20:08:35 UTC 
Good day

It has been some time since i was able to provide the cu with an update.

Can you please advise current status/thoughts, subsequent to the last update.

Mitch
Comment 9 Mitchell Rollinson 2019-01-14 19:36:33 UTC 
Please advise if you require any additional information in order to move this forward.

Mitch
Comment 10 Mitchell Rollinson 2019-01-31 19:25:09 UTC 
The cu has recently performed an update to v3.11.43
During which the cu encountered the same issue.

Please advise if you require any additional information in order to proceed this BZ.
Comment 11 Mitchell Rollinson 2019-02-28 00:44:11 UTC 
Good day, Would you have any updates/feedback, that i can pass onto the customer.
Comment 12 Brenton Leanhardt 2019-03-05 16:51:27 UTC 
*** Bug 1646207 has been marked as a duplicate of this bug. ***
Comment 13 Patrick Dillon 2019-03-14 20:36:13 UTC 
This is a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1684484

As with that bug, we recommend that you give your certificates distinct filenames so they will not be overwritten.

*** This bug has been marked as a duplicate of bug 1684484 ***