origin: Deployment fails unexpectedly

I’ve created 30 builds via:

for i in $( seq 1 30 ); do oc new-project gogo$i && oc new-app --template=“redmine”; done

And some of them failed with:

I0305 16:43:02.072052 1 recreate.go:131] Performing acceptance check of gogo28/redmine-app-1 4 I0305 16:43:02.072136 1 lifecycle.go:445] Waiting 600 seconds for pods owned by deployment "gogo28/redmine-app-1" to become ready (checking every 1 seconds; 0 pods previously accepted) 5 F0305 16:53:02.072349 1 deployer.go:69] update acceptor rejected gogo28/redmine-app-1: pods for deployment "gogo28/redmine-app-1" took longer than 600 seconds to become ready

I got five bare metal servers each with 16GB of RAM 4 cores and they are located in one rack.

Can this issue be caused by creating too many instances at once? Another problem is that there are no events in event log for this particular deployments (deployments which failed).

About this issue

Original URL
State: closed
Created 8 years ago
Comments: 18 (7 by maintainers)

Most upvoted comments

This error means that the pods the deployer is trying to deploy have never become ready. That could be a variety of different things which is why @kargakis requested logs. The steps you can take to try and diagnose this further are:

look for failed containers of the image you are trying to deploy and check out their logs in docker. Perhaps the containers are failing and preventing the deployment from completing.
review probes you have defined for the container in your pod spec. Is the probe defined correctly or is there an issue that would prevent readiness?
review the logs of the deployment and look for errors

This issue is becoming a bit confused with different postings. Each image running into this issue could be suffering from its own problems. Since the original requestor has not responded with logs I’m going to close this with the suggestion that folks open their own unique issue with the detailed logs and resource definitions.

pweil- on Jul 12, 2017

Comments above were edited to remove certificate data. Better safe than sorry 😄

pweil- on Apr 5, 2017