Description of problem: Installing openshift v3.10.0-0.66 fails, control plan pods dont come up ok. Version-Release number of selected component (if applicable): openshift v3.10.0-0.66 Client: Version: 1.13.1 API version: 1.26 Package version: docker-1.13.1-66.gitdded712.el7.x86_64 Go version: go1.9.2 Git commit: dded712/1.13.1 Built: Mon Jun 11 11:42:40 2018 OS/Arch: linux/amd64 Server: Version: 1.13.1 API version: 1.26 (minimum version 1.12) Package version: docker-1.13.1-66.gitdded712.el7.x86_64 Go version: go1.9.2 Git commit: dded712/1.13.1 Built: Mon Jun 11 11:42:40 2018 OS/Arch: linux/amd64 Experimental: false How reproducible: with build v3.10.0-0.66 Steps to Reproduce: 1. Use attached inventory to install v3.10.0-0.66 2. see ansible and journal logs attached. Actual results: Install fails because control plane pods didn't come up Expected results: Install should complete Additional info:
Created attachment 1450585 [details] ansible log with -vvv
Created attachment 1450586 [details] master journal logs
From the journal: Jun 12 17:27:01 ip-172-31-50-118.us-west-2.compute.internal dockerd-current[2960]: time="2018-06-12T17:27:01.62026041Z" level=error msg="containerd: start container" error="oci runtime error: container_linux.go:247: starting container process caused \"process_linux.go:258: applying cgroup configuration for process caused \\\"No such device or address\\\"\"\n" id=ed4f17954b558e1089b8f09f9e6f2c51a79ff1d51dd8c046f4a6641d10daa745 Jun 12 17:27:01 ip-172-31-50-118.us-west-2.compute.internal dockerd-current[2960]: time="2018-06-12T17:27:01.620586168Z" level=error msg="Create container failed with error: oci runtime error: container_linux.go:247: starting container process caused \"process_linux.go:258: applying cgroup configuration for process caused \\\"No such device or address\\\"\"\n"
Can we retry with the latest docker build https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=709971?
Works with following docker version docker.x86_64 2:1.13.1-68.gitdded712.el7
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-2018:1816