Bug 1573721 - [online-int]Failed to create applications with templates
Summary: [online-int]Failed to create applications with templates
Keywords:
Status: VERIFIED
Alias: None
Product: OpenShift Online
Classification: Red Hat
Component: Website
Version: unspecified
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: Abhishek Gupta
QA Contact: yasun
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-05-02 06:46 UTC by wewang
Modified: 2018-05-02 10:04 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:


Attachments (Terms of Use)

Description wewang 2018-05-02 06:46:16 UTC
Description of problem:
0/9 nodes are available when creating application with existed templates

Version-Release number of selected component (if applicable):
v3.9.14 (online version 3.6.0.90) 

How reproducible:
always

Steps to Reproduce:
1.oc new-app django-psql-persistent
2.oc get pods
$ oc get pods --watch
NAME                                READY     STATUS      RESTARTS   AGE
cakephp-mysql-persistent-1-build    0/1       Completed   0          1m
cakephp-mysql-persistent-1-deploy   0/1       Error       0          28s
mysql-1-deploy                      1/1       Running     0          1m
mysql-1-nvkw8                       0/1       Pending     0          1m

3.Describe  the pod
$ oc describe pod mysql-1-nvkw8
Name:           mysql-1-nvkw8
Namespace:      php
Node:           <none>
Labels:         deployment=mysql-1
                deploymentconfig=mysql
                name=mysql
Annotations:    kubernetes.io/limit-ranger=LimitRanger plugin set: cpu request for container mysql; cpu limit for container mysql
                openshift.io/deployment-config.latest-version=1
                openshift.io/deployment-config.name=mysql
                openshift.io/deployment.name=mysql-1
                openshift.io/generated-by=OpenShiftNewApp
                openshift.io/scc=restricted
Status:         Pending
IP:             
Controlled By:  ReplicationController/mysql-1
Containers:
  mysql:
    Image:      docker-registry.default.svc:5000/openshift/mysql@sha256:96ba047263b37e769a01bf62b384c122477a82a56a8e2477de85b8355d4459da
    Port:       3306/TCP
    Host Port:  0/TCP
    Limits:
      cpu:     1
      memory:  512Mi
    Requests:
      cpu:      80m
      memory:   409Mi
    Liveness:   tcp-socket :3306 delay=30s timeout=1s period=10s #success=1 #failure=3
    Readiness:  exec [/bin/sh -i -c MYSQL_PWD='fEpYWCIymO2fkP8B' mysql -h 127.0.0.1 -u cakephp -D default -e 'SELECT 1'] delay=5s timeout=1s period=10s #success=1 #failure=3
    Environment:
      MYSQL_USER:      <set to the key 'database-user' in secret 'cakephp-mysql-persistent'>      Optional: false
      MYSQL_PASSWORD:  <set to the key 'database-password' in secret 'cakephp-mysql-persistent'>  Optional: false
      MYSQL_DATABASE:  default
    Mounts:
      /var/lib/mysql/data from mysql-data (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-t4tfk (ro)
Conditions:
  Type           Status
  PodScheduled   False 
Volumes:
  mysql-data:
    Type:       PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
    ClaimName:  mysql
    ReadOnly:   false
  default-token-t4tfk:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  default-token-t4tfk
    Optional:    false
QoS Class:       Burstable
Node-Selectors:  type=compute
Tolerations:     node.kubernetes.io/memory-pressure:NoSchedule
Events:
  Type     Reason            Age                From               Message
  ----     ------            ----               ----               -------
  Warning  FailedScheduling  12s (x14 over 2m)  default-scheduler  0/9 nodes are available: 1 NodeUnschedulable, 3 Insufficient cpu, 5 MatchNodeSelector.


Actual results:
pods cannot be runing

Expected results:
pods are running

Additional info:
other templates had the same problem


Note You need to log in before you can comment on or make changes to this bug.