Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1424629

Summary: Router and Registry pods do not start on atomic host OCP
Product: OpenShift Container Platform Reporter: Vikas Laad <vlaad>
Component: NodeAssignee: Paul Morie <pmorie>
Status: CLOSED NOTABUG QA Contact: DeShuai Ma <dma>
Severity: high Docs Contact:
Priority: high    
Version: 3.5.0CC: aos-bugs, jokerman, mifiedle, mmccomas, pweil, wmeng
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1425583 (view as bug list) Environment:
Last Closed: 2017-02-20 21:31:55 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1425583    

Description Vikas Laad 2017-02-17 20:56:55 UTC
Description of problem:
Router and registry pods do not come up when installing OCP on atomic host.

Version-Release number of selected component (if applicable):
openshift v3.5.0.31-1+d55d08f
kubernetes v1.5.2+43a9be4
etcd 3.1.0

How reproducible:
Always

Steps to Reproduce:
1. Create atomic host OCP env
2. after running openshift-ansible paybook see the pods

-bash-4.2# oc get pods -n default
NAME                        READY     STATUS              RESTARTS   AGE
docker-registry-7-deploy    0/1       ContainerCreating   0          16m
registry-console-1-deploy   0/1       ContainerCreating   0          16m
router-1-deploy             0/1       ContainerCreating   0          17m

Failed events from registry pod
  21m		13s		98	{kubelet ip-172-31-56-82.us-west-2.compute.internal}			Warning		FailedSync	Error syncing pod, skipping: failed to "StartContainer" for "POD" with RunContainerError: "runContainer: Error response from daemon: Invalid --security-opt: \"label=level:s0:c1,c0\""

Failed events from router pod
  23m		13s		107	{kubelet ip-172-31-56-82.us-west-2.compute.internal}			Warning		FailedSync	Error syncing pod, skipping: failed to "StartContainer" for "POD" with RunContainerError: "runContainer: Error response from daemon: Invalid --security-opt: \"label=level:s0:c1,c0\""

Actual results:
Registry and Router in stuck in ContainerCreating

Expected results:
Registry and Router should be running.

Additional info:

Comment 1 DeShuai Ma 2017-02-20 13:38:31 UTC
what's the docker version?
FYI: https://github.com/openshift/origin/pull/12831#issuecomment-280329639

Comment 2 Vikas Laad 2017-02-20 14:38:17 UTC
-bash-4.2# docker version
Client:
 Version:         1.10.3
 API version:     1.22
 Package version: docker-common-1.10.3-44.el7.x86_64
 Go version:      go1.4.2
 Git commit:      7ffc8ee-unsupported
 Built:           Fri Jun 17 15:27:21 2016
 OS/Arch:         linux/amd64

Server:
 Version:         1.10.3
 API version:     1.22
 Package version: docker-common-1.10.3-44.el7.x86_64
 Go version:      go1.4.2
 Git commit:      7ffc8ee-unsupported
 Built:           Fri Jun 17 15:27:21 2016
 OS/Arch:         linux/amd64

Comment 3 Paul Weil 2017-02-20 16:17:38 UTC
docker 1.12 is a minimum requirement for 3.5  and should not suffer from this issue.  Also, please note that this was fixed upstream in https://github.com/kubernetes/kubernetes/pull/40946 with a version checking method that can set the separator correctly.  We should get that into OpenShift.

Comment 4 Paul Morie 2017-02-20 21:31:55 UTC
The issue is that an unsupported docker is being used; use docker 1.12