Description of problem: Version-Release number of the following components: 4.0.0-0.nightly-2019-04-03-202419 How reproducible: Always Steps to Reproduce: 1. Follow https://github.com/openshift/installer/blob/master/docs/user/aws/install_upi.md, use cloudformation templates to set up upi on aws 2. After env is set up, check any pod log. 3. Actual results: # oc logs cluster-version-operator-666bfb9fd5-bj9zv -n openshift-cluster-version Error from server: Get https://ip-10-0-49-186.us-east-2.compute.internal:10250/containerLogs/openshift-cluster-version/cluster-version-operator-666bfb9fd5-bj9zv/cluster-version-operator: remote error: tls: internal error Expected results: could get pod logs successfully. Additional info: workaround: # oc get csr --no-headers|grep -i pending|awk '{print $1}' | xargs oc adm certificate approve
user provisioned infrastructure *requires* users to perform additional actions like approving certificates for nodes.
In UPI on aws doc [1], there is no any hint to ask user to perform additional actions like approving certificates for nodes. If need user do it manually, pls add such steps in the doc. [1]: https://github.com/openshift/installer/blob/master/docs/user/aws/install_upi.md#option-2-manually-launching-worker-instances
Hit the same issue for UPI on vmware. The same workaround can resolve.
https://github.com/openshift/installer/pull/1594
Verified this bug with 4.0.0-0.nightly-2019-04-10-182914 and following the latest doc, it succeed.
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://access.redhat.com/errata/RHBA-2019:0758