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
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.
Good day, May i have a case update for the cu please. Thanks Mitch
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
Please advise if you require any additional information in order to move this forward. Mitch
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.
Good day, Would you have any updates/feedback, that i can pass onto the customer.
*** Bug 1646207 has been marked as a duplicate of this bug. ***
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 ***