Bug 1851445

Summary: [OSP13->OSP16.1] FFU fails with Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)
Product: Red Hat OpenStack Reporter: Jose Luis Franco <jfrancoa>
Component: openstack-tripleo-heat-templatesAssignee: Jesse Pretorius <jpretori>
Status: CLOSED ERRATA QA Contact: Ronnie Rasouli <rrasouli>
Severity: medium Docs Contact:
Priority: medium    
Version: 16.1 (Train)CC: jpretori, mburns, rrasouli
Target Milestone: z2Keywords: Triaged
Target Release: 16.1 (Train on RHEL 8.2)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-tripleo-heat-templates-11.3.2-0.20200728213431.6c7ccc9.el8ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-10-28 15:38:11 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jose Luis Franco 2020-06-26 14:22:19 UTC
Description of problem:

When performing the FFU upgrade from OSP13 to OSP16.1, during the Undercloud upgrade step the upgrade fails in the mysql_neutron_db_rename container with the following error:

2020-06-26T09:15:28.976248074-04:00 stderr F ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)

This looks like it's caused by a race condition between mysql and this container, as the DB isn't up and running yet when the container gets executed. It tends to occur in system with slow HDD or virtualized environments.

To workaround the issue it is possible to restart the container and just re-run the whole undercloud upgrade command:

* sudo podman restart mysql_neutron_db_rename
* openstack undercloud upgrade -y

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 7 errata-xmlrpc 2020-10-28 15:38:11 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 (Red Hat OpenStack Platform 16.1 bug fix and enhancement 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/RHEA-2020:4284