Train -> Ussuri undercloud upgrade failing with on pymysql.err.OperationalError: (2003, "Can't connect to MySQL server on '192.168.24.3' ([Errno 113] No route to host)")
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
Critical
|
Alex Schultz |
Bug Description
Description:-
Train -> Ussuri undercloud upgrade failing with on pymysql.
Log snippet:-
https:/
~~~
2021-05-30 01:20:41 | 2021-05-30 01:20:41.541278 | fa163e91-
2021-05-30 01:26:03 | [ERROR]: Container(s) which finished with wrong return code:
2021-05-30 01:26:03 | ['mistral_db_sync', 'glance_
2021-05-30 01:26:03 | [ERROR]: Container(s) which failed to be created by podman_container module:
2021-05-30 01:26:03 | ['keystone_
2021-05-30 01:26:03 | [ERROR]: Container(s) which did not finish after 300 minutes:
2021-05-30 01:26:03 | ['keystone_
2021-05-30 01:26:03 | 2021-05-30 01:26:03.365437 | fa163e91-
~~~
~~~
CRITI [Mistral] Unhandled error
Traceback (most recent call last):
File "/usr/lib/
**kwargs)
File "/usr/lib64/
raise err
File "/usr/lib64/
sock.
OSError: [Errno 113] No route to host
During handling of the above exception, another exception occurred:
.
.
sqlalchemy.
(Background on this error at: http://
~~~
~~~
2021-05-30 01:38:58.414 7 WARNING oslo_db.
~~~
Another example:
Changed in tripleo: | |
importance: | Undecided → Critical |
Changed in tripleo: | |
assignee: | nobody → Alex Schultz (alex-schultz) |
status: | Triaged → In Progress |
Changed in tripleo: | |
milestone: | xena-1 → xena-2 |
Changed in tripleo: | |
status: | In Progress → Fix Released |
Related fix proposed to branch: master /review. opendev. org/c/openstack /tripleo- ci/+/793693
Review: https:/