Description of problem: Pod cannot startup if create with default installed mysql ephemeral template and below error appears when describe failed pod: Events: FirstSeen LastSeen Count From SubobjectPath Type Reason Message --------- -------- ----- ---- ------------- -------- ------ ------- <invalid> <invalid> 1 {default-scheduler } Normal Scheduled Successfully assigned mysql-1-zkj7e to openshift-150.lab.sjc.redhat.com <invalid> <invalid> 1 {kubelet openshift-150.lab.sjc.redhat.com} spec.containers{mysql} Normal Pulled Container image "brew-pulp-docker01.web.prod.ext.phx2.redhat.com:8888/rhscl/mysql-56-rhel7:latest" already present on machine <invalid> <invalid> 1 {kubelet openshift-150.lab.sjc.redhat.com} spec.containers{mysql} Normal Created Created container with docker id 62a09abd97e9 <invalid> <invalid> 1 {kubelet openshift-150.lab.sjc.redhat.com} spec.containers{mysql} Normal Started Started container with docker id 62a09abd97e9 <invalid> <invalid> 1 {kubelet openshift-150.lab.sjc.redhat.com} spec.containers{mysql} Warning Unhealthy 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) <invalid> <invalid> 1 {kubelet openshift-150.lab.sjc.redhat.com} spec.containers{mysql} Warning Unhealthy Readiness probe failed: sh: cannot set terminal process group (-1): Inappropriate ioctl for device sh: no job control in this shell ERROR 1045 (28000): Access denied for user 'userD64'@'127.0.0.1' (using password: YES) Version-Release number of selected component (if applicable): openshift v3.2.0.5 kubernetes v1.2.0-36-g4a3f9c5 etcd 2.2.5 How reproducible: always Steps to Reproduce: 1. Log into web console 2. Create a project 3. Add mysql-ephemeral template to project 4. Check pod status 5. Describe pod Actual results: 4. Pod cannot startup 5. There are errors in Event Expected results: Pod should be running Additional info: mongodb/postgresql ephemeral template failed for the same reason some time.
mysql-persistent template also has such issue.
Michal, looks like a problem w/ the new readiness probes.
suspect this is fixed by this pull also: https://github.com/openshift/origin/pull/8208
*** This bug has been marked as a duplicate of bug 1320335 ***
There is also a problem starting if the mysql userid/pw are customized as well. The acceptance test fails even though you can rsh into the pod and issue the mysql command successfully.