Deployment in new state for 2 days

[smarterclayton]

Unusual deployment, in "new" for 2 days on a 3.7 cluster:

oc describe dc -n XX X-staging
Name:		X-staging
Namespace:	pc2
Created:	2 days ago
Labels:		<none>
Annotations:	<none>
Latest Version:	1
Selector:	deploymentconfig=X-staging
Replicas:	1
Triggers:	Config
Strategy:	Rolling
Template:
Pod Template:
  Labels:	deploymentconfig=X-staging
  Containers:
   X-staging:
    Image:	3scale-amp20/apicast-gateway:1.0-3
    Ports:	8080/TCP, 8090/TCP
    Liveness:	http-get http://:8090/status/live delay=10s timeout=5s period=10s #success=1 #failure=3
    Readiness:	http-get http://:8090/status/ready delay=15s timeout=5s period=30s #success=1 #failure=3
    Environment:
      APICAST_CONFIGURATION_LOADER:	lazy
      APICAST_CONFIGURATION_CACHE:	0
      THREESCALE_DEPLOYMENT_ENV:	sandbox
      APICAST_MANAGEMENT_API:		status
      OPENSSL_VERIFY:			false
      APICAST_RESPONSE_CODES:		true
    Mounts:				<none>
  Volumes:				<none>

Deployment #1 (latest):
	Name:		X-staging-1
	Created:	2 days ago
	Status:		New
	Replicas:	0 current / 0 desired
	Selector:	deployment=X-staging-1,deploymentconfig=X-staging
	Labels:		openshift.io/deployment-config.name=X-staging
	Pods Status:	0 Running / 0 Waiting / 0 Succeeded / 0 Failed

Events:	<none>

This deployment should be failed or complete, not New.

@openshift/sig-master

[tnozicka]

@smarterclayton can you pls dump YAML for the DC,RC and deployer pod?

[mfojtik]

Whatever happened here, we should always respect the timeoutSeconds which defaults to 10 minutes. After 10 minutes this should transition from New to Failed since there was no progress. It would be interesting to know why this got stuck, I assume it failed to create the deployer pod because of quota(?) or some other non-transient error. Maybe we should print the last condition here to see where it got stuck.