Description of problem: tokenization[1] can fail[2][3][4] without error. [1]: https://github.com/openshift/machine-config-operator/blob/b135a37d0e380c904fe5397b68a71a3bf33a10ba/templates/master/00-master/_base/files/usr-local-bin-etcd-member-recover-sh.yaml#L71 [2]: https://storage.googleapis.com/origin-ci-test/logs/release-openshift-origin-installer-e2e-aws-disruptive-4.3/3/build-log.txt [3]: https://storage.googleapis.com/origin-ci-test/logs/release-openshift-origin-installer-e2e-aws-disruptive-4.3/3/artifacts/e2e-aws-disruptive/pods/openshift-etcd_etcd-member-ip-10-0-142-1.ec2.internal_certs.log [4]: https://storage.googleapis.com/origin-ci-test/logs/release-openshift-origin-installer-e2e-aws-disruptive-4.3/3/artifacts/e2e-aws-disruptive/pods/openshift-etcd_etcd-member-ip-10-0-142-1.ec2.internal_certs_previous.log Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: If tokenization fails exit non 0 and print error. Additional info:
@Sam Batschelet, I'm confuse somewhat, log[2][3][4] have error msg already, then why we still need exit with non 0 and print err?
Hi Sam, it there any update? thx
*** Bug 1758681 has been marked as a duplicate of this bug. ***
Thank you Suresh.
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-2020:0062