Because events are TTL'd they'll vanish after two hours. If an admin runs `openshift-installer wait-for bootstrap-complete` after that point it won't know whether bootstrap has completed or not and would need to check on a different long lived condition.
Verified this bug with 4.0.0-0.nightly-2019-04-18-190537, and PASS. # ./20190419_1/openshift-install version ./20190419_1/openshift-install v4.1.0-201904181302-dirty built from commit b79562d600f72d0f70aa1514b01e6c07da4dcc8a release image registry.svc.ci.openshift.org/ocp/release:4.0.0-0.nightly-2019-04-18-190537 # ./20190419_1/openshift-install wait-for bootstrap-complete --dir ./20190419_1/demo1 INFO Waiting up to 30m0s for the Kubernetes API at https://api.qe-jialiu.qe.devcluster.openshift.com:6443... INFO API v1.13.4+ff82892 up INFO Waiting up to 30m0s for bootstrapping to complete... INFO It is now safe to remove the bootstrap resources Reproduced on old version: After installation is completed, run again the command, the command would be pending there. # ./20190412/openshift-install version ./20190412/openshift-install v4.1.0-201904101232-dirty built from commit 741d4db20a2d673eb79cf6dbd076001c9cb65753 release image registry.svc.ci.openshift.org/ocp/release:4.0.0-0.nightly-2019-04-10-182914 # ./20190412/openshift-install wait-for bootstrap-complete --dir 20190419_1/demo1 INFO Waiting up to 30m0s for the Kubernetes API at https://api.qe-jialiu.qe.devcluster.openshift.com:6443... INFO API v1.13.4+ff82892 up INFO Waiting up to 30m0s for the bootstrap-complete event... ^C
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