Notes for QA
============

This should reproduce the issue (according to info from @bnater, who originally reproduced it on in-place upgrade workshop).

    {
        echo 'DROP DATABASE php_mysql_test;'
        echo 'CREATE DATABASE php_mysql_test;'
        echo 'USE php_mysql_test;'
        echo 'CREATE TABLE foobar (name VARCHAR(10), value INTEGER);'
        echo 'INSERT INTO foobar VALUES("fish", 42);'
    } | mysql --verbose -u root
   preupg --force

...and preupg will get stuck at mysql module mysql/general_changes.

Also, make sure to review the patch:

    http://git.app.eng.bos.redhat.com/git/preupgrade-assistant-contents.git/commit/?h=rhel6_7-post&id=e91c3b4b452b8c194d350f81cd5d33c02573ef60

(Correcting Alois Mahdal's comment #3)
> Notes for QA
> ============
> 
> This should reproduce the issue (according to info from @bnater, who
> originally reproduced it on in-place upgrade workshop).


Of course, first:

    yum -y install mysql mysql-server
    service mysql start

...then:

>     {
>         echo 'DROP DATABASE php_mysql_test;'
>         echo 'CREATE DATABASE php_mysql_test;'
>         echo 'USE php_mysql_test;'
>         echo 'CREATE TABLE foobar (name VARCHAR(10), value INTEGER);'
>         echo 'INSERT INTO foobar VALUES("fish", 42);'
>     } | mysql --verbose -u root
>    preupg --force

Turns out that /CoreOS/preupgrade-assistant-el6toel7/upg/mysql-sanity reproduces this as well, so I used that instead of the above STR.

 *  TJ#1959725 preupgrade-assistant-el6toel7-0.6.70-2.el6 - is still
    stuck at the mysql module.

 *  TJ#1959724 preupgrade-assistant-el6toel7-0.6.71-2.el6 - has already
    finished and passed.

 *  I have reviewed the texts and terms are now quoted using apostrophes.

 *  I have also reviewed the patch -- looks OK.

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.

https://access.redhat.com/errata/RHBA-2017:2400