Description of problem: The bootkube service failed in a 4.2 upi-on-vsphere install as below: [core@bootstrap-0 ~]$ journalctl -f -u bootkube.service -- Logs begin at Fri 2019-08-09 02:59:01 UTC. -- Aug 09 05:22:15 bootstrap-0 systemd[1]: Started Bootstrap a Kubernetes cluster. Aug 09 05:22:26 bootstrap-0 bootkube.sh[11789]: Starting etcd certificate signer... Aug 09 05:22:26 bootstrap-0 bootkube.sh[11789]: Cannot use two forms of the same flag: network net Aug 09 05:22:26 bootstrap-0 bootkube.sh[11789]: See 'podman run --help'. Aug 09 05:22:26 bootstrap-0 systemd[1]: bootkube.service: Main process exited, code=exited, status=125/n/a Aug 09 05:22:26 bootstrap-0 systemd[1]: bootkube.service: Failed with result 'exit-code'. Version-Release number of the following components: registry.svc.ci.openshift.org/ocp/release:4.2.0-0.nightly-2019-08-08-103722 [core@bootstrap-0 ~]$ rpm-ostree status State: idle AutomaticUpdates: disabled Deployments: ● pivot://quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:7425a864b498dc18166ffdfeb14f500292e9681c854852d89f919c5b56203630 CustomOrigin: Provisioned from oscontainer Version: 410.8.20190509.3 (2019-05-09T11:53:46Z) [core@bootstrap-0 ~]$ podman --version podman version 1.0.2-dev How reproducible: Always Steps to Reproduce: 1. 2. 3. Actual results: Please include the entire output from the last TASK line through the end of output if an error is generated Expected results: Additional info:
https://github.com/openshift/installer/pull/2171 should have fixed this.
Verified with payload 4.2.0-0.nightly-2019-08-10-002649, bootstrap completed successfully.
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:2922