Bug 1320015 - Pod cannot startup if create with default installed mysql-ephemeral/persistent template
Summary: Pod cannot startup if create with default installed mysql-ephemeral/persisten...
Keywords:
Status: CLOSED DUPLICATE of bug 1320335
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Templates
Version: 3.2.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Michal Fojtik
QA Contact: XiuJuan Wang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-22 06:34 UTC by Wenjing Zheng
Modified: 2016-03-23 19:56 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-03-23 19:56:23 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Wenjing Zheng 2016-03-22 06:34:47 UTC
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.

Comment 1 Wenjing Zheng 2016-03-22 07:30:32 UTC
mysql-persistent template also has such issue.

Comment 2 Ben Parees 2016-03-22 13:20:51 UTC
Michal, looks like a problem w/ the new readiness probes.

Comment 3 Ben Parees 2016-03-23 19:55:37 UTC
suspect this is fixed by this pull also:
https://github.com/openshift/origin/pull/8208

Comment 4 Ben Parees 2016-03-23 19:56:23 UTC

*** This bug has been marked as a duplicate of bug 1320335 ***

Comment 5 Mike Fiedler 2016-03-23 19:56:35 UTC
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.


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