+++ This bug was initially created as a clone of Bug #1820145 +++
Description of problem:
UPI Vmware test runs fail with invalid internal LB hostname in certificates
Version-Release number of selected component (if applicable):
@Stefan, Could you point me the related error message in https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/release-openshift-ocp-installer-e2e-vsphere-upi-4.4/1357?
I guess just like below, right? I am not sure since I saw the change only one typo calling wrong internal LB in PR.
Mar 30 10:33:23.303: FAIL: Get https://api.ci-op-7zg3gn6s-e99c3.origin-ci-int-aws.dev.rhcloud.com:6443/apis/user.openshift.io/v1/users/~: x509: certificate is valid for api.ci-op-4byd7z0v-3858a.origin-ci-int-aws.dev.rhcloud.com, not api.ci-op-7zg3gn6s-e99c3.origin-ci-int-aws.dev.rhcloud.com
To verify this bug, I just check no related errors in install log, is this enough? If you have comments about this, let me know. Thanks.
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.