Attachment 1451463 Details for Bug 1591145 – Describe showing old warning, but pod Ready

Describe showing old warning, but pod Ready

file_1591145.txt (text/plain), 4.79 KB, created by Justin Pierce on 2018-06-14 16:39:07 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Justin Pierce

Created: 2018-06-14 16:39:07 UTC

Size: 4.79 KB

patch

obsolete

>[root@free-stg-master-03fb6 ~]# oc describe pod mysql-1-s9cdq
>Name:           mysql-1-s9cdq
>Namespace:      jmp-test13
>Node:           ip-172-31-70-31.us-east-2.compute.internal/172.31.70.31
>Start Time:     Thu, 14 Jun 2018 16:27:12 +0000
>Labels:         app=mysql-persistent
>                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:         Running
>IP:             10.130.8.153
>Controlled By:  ReplicationController/mysql-1
>Containers:
>  mysql:
>    Container ID:   docker://b8c2716b6ec7c75ebf7f2d4b8832002387a5d1bc2b2b530e84928471c8eccd67
>    Image:          docker-registry.default.svc:5000/openshift/mysql@sha256:01c59852b0c720322598a5370ed93038e04af101b1e3ee55a1aab77bf600a7af
>    Image ID:       docker-pullable://docker-registry.default.svc:5000/openshift/mysql@sha256:01c59852b0c720322598a5370ed93038e04af101b1e3ee55a1aab77bf600a7af
>    Port:           3306/TCP
>    Host Port:      0/TCP
>    State:          Running
>      Started:      Thu, 14 Jun 2018 16:27:26 +0000
>    Ready:          True
>    Restart Count:  0
>    Limits:
>      cpu:     1
>      memory:  512Mi
>    Requests:
>      cpu:      50m
>      memory:   256Mi
>    Liveness:   tcp-socket :3306 delay=30s timeout=1s period=10s #success=1 #failure=3
>    Readiness:  exec [/bin/sh -i -c MYSQL_PWD="$MYSQL_PASSWORD" mysql -h 127.0.0.1 -u $MYSQL_USER -D $MYSQL_DATABASE -e 'SELECT 1'] delay=5s timeout=1s period=10s #success=1 #failure=3
>    Environment:
>      MYSQL_USER:           <set to the key 'database-user' in secret 'mysql'>           Optional: false
>      MYSQL_PASSWORD:       <set to the key 'database-password' in secret 'mysql'>       Optional: false
>      MYSQL_ROOT_PASSWORD:  <set to the key 'database-root-password' in secret 'mysql'>  Optional: false
>      MYSQL_DATABASE:       <set to the key 'database-name' in secret 'mysql'>           Optional: false
>    Mounts:
>      /var/lib/mysql/data from mysql-data (rw)
>      /var/run/secrets/kubernetes.io/serviceaccount from default-token-cgq79 (ro)
>Conditions:
>  Type           Status
>  Initialized    True 
>  Ready          True 
>  PodScheduled   True 
>Volumes:
>  mysql-data:
>    Type:       PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
>    ClaimName:  mysql
>    ReadOnly:   false
>  default-token-cgq79:
>    Type:        Secret (a volume populated by a Secret)
>    SecretName:  default-token-cgq79
>    Optional:    false
>QoS Class:       Burstable
>Node-Selectors:  type=compute
>Tolerations:     node.kubernetes.io/memory-pressure:NoSchedule
>Events:
>  Type     Reason                  Age   From                                                 Message
>  ----     ------                  ----  ----                                                 -------
>  Normal   Scheduled               8m    default-scheduler                                    Successfully assigned mysql-1-s9cdq to ip-172-31-70-31.us-east-2.compute.internal
>  Warning  FailedAttachVolume      8m    attachdetach-controller                              AttachVolume.Attach failed for volume "pvc-c929d3c9-6fef-11e8-a275-02306c0cdc4b" : "Error attaching EBS volume \"vol-0b55f36f294c64e3a\"" to instance "i-0fc539840d34a05ba" since volume is in "creating" state
>  Normal   SuccessfulAttachVolume  8m    attachdetach-controller                              AttachVolume.Attach succeeded for volume "pvc-c929d3c9-6fef-11e8-a275-02306c0cdc4b"
>  Normal   Pulling                 8m    kubelet, ip-172-31-70-31.us-east-2.compute.internal  pulling image "docker-registry.default.svc:5000/openshift/mysql@sha256:01c59852b0c720322598a5370ed93038e04af101b1e3ee55a1aab77bf600a7af"
>  Normal   Pulled                  8m    kubelet, ip-172-31-70-31.us-east-2.compute.internal  Successfully pulled image "docker-registry.default.svc:5000/openshift/mysql@sha256:01c59852b0c720322598a5370ed93038e04af101b1e3ee55a1aab77bf600a7af"
>  Normal   Created                 8m    kubelet, ip-172-31-70-31.us-east-2.compute.internal  Created container
>  Normal   Started                 8m    kubelet, ip-172-31-70-31.us-east-2.compute.internal  Started container
>  Warning  Unhealthy               8m    kubelet, ip-172-31-70-31.us-east-2.compute.internal  Readiness probe failed: sh: cannot set terminal process group (-1): Inappropriate ioctl for device
>sh: no job control in this shell
>ERROR 2003 (HY000): Can't connect to MySQL server on '127.0.0.1' (111)

Actions: View

Attachments on bug 1591145: 1451463