Bug 1583895 - [APB] mysql-apb update from 5.6 to 5.7 failed
Summary: [APB] mysql-apb update from 5.6 to 5.7 failed
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Service Broker
Version: 3.9.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 3.9.z
Assignee: Jason Montleon
QA Contact: Zihan Tang
Depends On:
TreeView+ depends on / blocked
Reported: 2018-05-30 02:19 UTC by Zihan Tang
Modified: 2018-06-27 18:02 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Last Closed: 2018-06-27 18:02:09 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2018:2013 normal SHIPPED_LIVE Important: OpenShift Container Platform 3.9 security, bug fix, and enhancement update 2018-06-27 22:01:43 UTC

Description Zihan Tang 2018-05-30 02:19:06 UTC
Description of problem:
mysql-apb update from 5.6 to 5.7 failed 

Version-Release number of selected component (if applicable):
mysql-apb: v3.9.27

How reproducible:

Steps to Reproduce:
1. provision mysql 5.6 
2. create data in mysql pod
3. upgrade to 5.7 in backend or web console

Actual results:
upgrade to 5.7 failed.

sandbox log:
# oc logs -f apb-ea16373c-6662-4162-aac0-3448b2d38c34

TASK [rhscl-mysql-apb-openshift : Restore database] ****************************
changed: [localhost]

TASK [rhscl-mysql-apb-openshift : Run mysql_upgrade] ***************************
fatal: [localhost]: FAILED! => {"changed": true, "cmd": "oc exec -it -n 1oz3n mysql-5.7-dev-1-mk9jq -- /bin/bash -c \"mysql_upgrade -u root\"", "delta": "0:00:00.776787", "end": "2018-05-23 08:58:46.823383", "msg": "non-zero return code", "rc": 2, "start": "2018-05-23 08:58:46.046596", "stderr": "Unable to use a TTY - input is not a terminal or the right kind of file\ncommand terminated with exit code 2", "stderr_lines": ["Unable to use a TTY - input is not a terminal or the right kind of file", "command terminated with exit code 2"], "stdout": "Checking if update is needed.\nThis installation of MySQL is already upgraded to 5.7.21, use --force if you still need to run mysql_upgrade", "stdout_lines": ["Checking if update is needed.", "This installation of MySQL is already upgraded to 5.7.21, use --force if you still need to run mysql_upgrade"]}

PLAY RECAP *********************************************************************
localhost                  : ok=12   changed=10   unreachable=0    failed=1   

the old pod is not deleted. but data has been moved to new pod
# oc get pod 
NAME                     READY     STATUS    RESTARTS   AGE
mysql-5.6-prod-1-qvpt5   1/1       Running   0          4m
mysql-5.7-dev-1-mk9jq    1/1       Running   0          3m

this is caused by mysql in dependency  registry.access.redhat.com/rhscl/mysql-57-rhel7 update to 5.7.21.

Additional info:
the same issue in v3.10 : 

Comment 6 Zihan Tang 2018-06-13 06:56:53 UTC
I use the image: v3.9.31 in brew registry to pre-test. It passed. 
I will wait for image ready in stage registry , change the status to Modified .

Comment 7 Zihan Tang 2018-06-15 06:24:27 UTC
image is ready , change it to ON_QA

Comment 8 Zihan Tang 2018-06-15 06:26:12 UTC
version: mysql-apb:v3.9.31

Comment 10 errata-xmlrpc 2018-06-27 18:02:09 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


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