Comment 1 for bug 1906822

still happening see [1].

doesn't appear to be glance specific so removed that from the title

In logs from yesterday [2] I see the same issue but in the keyston log:

  * 2020-12-13 20:00:56.150 27 DEBUG migrate.versioning.repository [-] Repository /usr/lib/python3.6/site-packages/keystone/common/sql/migrate_repo loaded successfully __init__ /usr/lib/python3.6/site-packages/migrate/versioning/repository.py:82
  2020-12-13 20:00:56.150 27 DEBUG migrate.versioning.repository [-] Config: OrderedDict([('db_settings', OrderedDict([('repository_id', 'keystone'), ('version_table', 'migrate_version'), ('required_dbs', '[]'), ('use_timestamp_numbering', 'False')]))]) __init__ /usr/lib/python3.6/site-packages/migrate/versioning/repository.py:83
  2020-12-13 20:00:59.295 27 WARNING oslo_db.sqlalchemy.engines [-] SQL connection failed. -1 attempts left.: oslo_db.exception.DBConnectionError: (pymysql.err.OperationalError) (2003, "Can't connect to MySQL server on '192.168.24.3' ([Errno 113] No route to host)")

I don't know if this is related to the bug at [3] yet - the error is happening in a different step though so really not sure about that (i.e. that it is a pacemaker version related issue).

[1] https://review.rdoproject.org/zuul/builds?job_name=periodic-tripleo-ci-centos-8-standalone-upgrade-tripleo-ussuri
[2] https://logserver.rdoproject.org/openstack-component-tripleo/opendev.org/openstack/tripleo-ci/master/periodic-tripleo-ci-centos-8-standalone-upgrade-tripleo-ussuri/0e7721a/logs/undercloud/var/log/containers/keystone/keystone.log.txt.gz
[3] https://bugs.launchpad.net/tripleo/+bug/1907769