Bug 1556720
Summary: | [OSP12] gnocchi-upgrade fails with InternalError: (1050, u"Table 'archive_policy' already exists") | |||
---|---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Michele Baldessari <michele> | |
Component: | openstack-tripleo-heat-templates | Assignee: | Michele Baldessari <michele> | |
Status: | CLOSED ERRATA | QA Contact: | Sasha Smolyak <ssmolyak> | |
Severity: | high | Docs Contact: | ||
Priority: | high | |||
Version: | 12.0 (Pike) | CC: | aschultz, jamsmith, mburns, michele, rhel-osp-director-maint, rscarazz | |
Target Milestone: | z3 | Keywords: | Triaged, ZStream | |
Target Release: | 12.0 (Pike) | |||
Hardware: | All | |||
OS: | Linux | |||
Whiteboard: | ||||
Fixed In Version: | openstack-tripleo-heat-templates-7.0.9-10.el7ost | Doc Type: | Bug Fix | |
Doc Text: |
To prevent failures caused by a gnocchi-upgrade race condition, gnocchi-upgrade is now called from the bootstrap node instead of from multiple nodes.
Previously, gnocchi-upgrade was called from each node where gnocchi-api is part of the role. This sometimes resulted in failures with the error shown in the following example:
2018-03-14 12:39:39,683 [1] ERROR oslo_db.sqlalchemy.exc_filters: DBAPIError exception wrapped from (pymysql.err.InternalError) (1050, u"Table 'archive_policy' already exists")
|
Story Points: | --- | |
Clone Of: | ||||
: | 1556721 (view as bug list) | Environment: | ||
Last Closed: | 2018-08-20 12:59:02 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
Michele Baldessari
2018-03-15 06:46:52 UTC
I verified the patch [1] on the same osp12 environment in which it was failing and it's working. [1] https://review.openstack.org/#/c/553028/1 Linked the proper pike/review The fixed-in-version is present, the fail doesn't happen anymore. Fixed 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/RHSA-2018:2331 |