Bug 1652287
Summary: | Deployment may fail because nova_wait_for_db_sync runs simultaneously on all three controllers | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Marius Cornea <mcornea> |
Component: | openstack-tripleo-heat-templates | Assignee: | Martin Schuppert <mschuppe> |
Status: | CLOSED ERRATA | QA Contact: | Gurenko Alex <agurenko> |
Severity: | urgent | Docs Contact: | |
Priority: | urgent | ||
Version: | 14.0 (Rocky) | CC: | asimonel, dbecker, egallen, jhakimra, lyarwood, mbooth, mburns, michele, morazi, mschuppe |
Target Milestone: | rc | Keywords: | Triaged |
Target Release: | 14.0 (Rocky) | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | openstack-tripleo-heat-templates-9.0.1-0.20181013060895.el7ost | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-01-11 11:54:47 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: | |||
Bug Depends On: | |||
Bug Blocks: | 1625732 |
Description
Marius Cornea
2018-11-21 19:30:55 UTC
I think these 2 errors represent 2 slightly different manifestations of the same race in nova's db_version(). We do: try: get db version except: count how many tables we've got if no tables: create a version table else: complain about an Essex-era db So if 2 threads execute this concurrently and both fail to get db version, we've then got a different behaviour based on whether the race winner has started creating the schema yet or not. If not, we get a 1050 as in the description. If yes, we get the Essex warning as in comment 3. The cause is the same, though. *** Bug 1636399 has been marked as a duplicate of this bug. *** *** Bug 1651475 has been marked as a duplicate of this bug. *** *** Bug 1653816 has been marked as a duplicate of this bug. *** Marking this as verified, after running multiple deployments with 3 controllers and didn't observe the faulty behavior. If this bug starts reappearing do not hesitate to reopen the bug. 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/RHEA-2019:0045 |