Bug 1505069
Summary: | heat-manage db_sync returns table and column collisions during upgrade | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Andrew Ludwar <aludwar> |
Component: | instack-undercloud | Assignee: | Emilien Macchi <emacchi> |
Status: | CLOSED ERRATA | QA Contact: | Gurenko Alex <agurenko> |
Severity: | urgent | Docs Contact: | |
Priority: | urgent | ||
Version: | 9.0 (Mitaka) | CC: | aschultz, emacchi, emilien, jjoyce, jschluet, knylande, mburns, rhel-osp-director-maint, sbaker, shardy, slinaber, srevivo, therve, tvignaud |
Target Milestone: | Upstream M2 | Keywords: | Triaged |
Target Release: | 13.0 (Queens) | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | instack-undercloud-8.1.1-0.20171206155308.5565e25.el7ost | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2018-06-27 13:38:59 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
Andrew Ludwar
2017-10-21 18:58:06 UTC
Updated the attached KCS article to reflect the steps taken to fix the issue. Essentially, they came down to these, but note these steps are very specific for where in the db_sync the failure occurred. These steps might not apply for every single db_sync failure. # mysql MariaDB [none]> use heat; MariaDB [heat]> alter table raw_template drop key raw_tmpl_files_fkey_ref;" MariaDB [heat]> alter table raw_template drop foreign key raw_tmpl_files_fkey_ref;" MariaDB [heat]> alter table raw_template drop column files_id;" MariaDB [heat]> drop table raw_template_files;" Additionally, the puppet timeout can be increased to allow for a larger heat DB time to sync: For future deployments, you could edit etc/puppet/manifests/puppet-stack-config.pp and change: Exec<| title == 'heat-dbsync' |> { refreshonly => false } to have: Exec<| title == 'heat-dbsync' |> { refreshonly => false, timeout => 900 } So the timeout will be set to 15 min for the Heat dbsync command. Keep in mind the undercloud upgrade command override this file, so you might need to edit the file right after running the upgrade command when instack-undercloud package is upgraded. You can also stop the Puppet run with CTLR+C before the Heat dbsync resource, edit the file, and run the upgrade command again. Reassigning, as the fix is to increase the timeout. Emilien can you ack? Thanks. Verified on puddle 2018-04-26.3 [stack@undercloud-0 ~]$ rpm -q instack-undercloud instack-undercloud-8.4.1-2.el7ost.noarch 2018-04-30 06:11:31,872 INFO: ############################################################################# Undercloud upgrade complete. openstack undercloud upgrade completed without any issues 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-2018:2086 |