We have an issue with a deployment. The deployer pod does not start.
Issue
- We just upgraded to openshift 3.2 and have the following issue:
I have a DC:
oc export dc app
apiVersion: v1
kind: DeploymentConfig
metadata:
annotations:
openshift.io/deployment.cancelled: "39"
openshift.io/generated-by: OpenShiftNewApp
creationTimestamp: null
labels:
app: app
name: app
spec:
replicas: 1
selector:
app: app
deploymentconfig: app
strategy:
resources:
limits:
cpu: 800m
memory: 1600Mi
requests:
cpu: 500m
memory: 800Mi
rollingParams:
intervalSeconds: 1
maxSurge: 25%
maxUnavailable: 0%
timeoutSeconds: 600
updatePeriodSeconds: 1
type: Rolling
template:
metadata:
annotations:
openshift.io/generated-by: OpenShiftNewApp
creationTimestamp: null
labels:
app: app
deploymentconfig: app
spec:
containers:
- env:
....
image: 172.30.x.x:5000/namespace/image@sha256:b54013a2321a7459eb22cb48ccb4245f1688a40974060b70db2a9bf864b59706
imagePullPolicy: IfNotPresent
name: app
ports:
- containerPort: 8080
protocol: TCP
readinessProbe:
failureThreshold: 3
httpGet:
path: /pages/x.xhtml
port: 8080
scheme: HTTP
initialDelaySeconds: 20
periodSeconds: 10
successThreshold: 1
timeoutSeconds: 10
resources:
limits:
cpu: 800m
memory: 1600Mi
requests:
cpu: 500m
memory: 800Mi
terminationMessagePath: /dev/termination-log
dnsPolicy: ClusterFirst
restartPolicy: Always
securityContext: {}
terminationGracePeriodSeconds: 30
test: false
triggers:
- type: ConfigChange
- imageChangeParams:
automatic: true
containerNames:
- app
from:
kind: ImageStreamTag
name: image:8-SNAPSHOT
namespace: namespace
type: ImageChange
status: {}
If we start a deployment for that config, we get an error (since upgrade to 3.2):
Error syncing pod, skipping: failed to "StartContainer" for "POD" with RunContainerError: "runContainer: API error (500): Cannot start container 90323e4a114cc36b6c65f76ad8d90e37b0675f0ae3f4f319bca6b4b926cb5402: [8] System error: read parent: connection reset by peer\n"
The deployer-pod cannot be started and now hangs on "Container Creating".
I found the issue (seems to be the same) on docker github: https://github.com/docker/docker/issues/14203
Seems to be fixed in docker 1.10. With OSE 3.2 we have now Docker 1.9.1.
Any suggestions?
Environment
- Openshift Enterprise 3.2.0
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.