Red Hat Bugzilla – Bug 1425116
OSP10 -> OSP11 upgrade fails during aodh-dbsync
Last modified: 2017-05-17 16:01:13 EDT
Description of problem: OSP10 -> OSP11 overcloud upgrade fails during aodh-dbsync: ProgrammingError: (pymysql.err.ProgrammingError) (1146, u"Table 'aodh.alarm_change' doesn't exist") [SQL: u'ALTER TABLE alarm_change ADD COLUMN timestamp_ts DATETIME(6)'] Version-Release number of selected component (if applicable): openstack-aodh-evaluator-4.0.1-0.20170210160347.e062a0a.el7ost.noarch openstack-aodh-common-4.0.1-0.20170210160347.e062a0a.el7ost.noarch openstack-aodh-notifier-4.0.1-0.20170210160347.e062a0a.el7ost.noarch openstack-aodh-listener-4.0.1-0.20170210160347.e062a0a.el7ost.noarch openstack-aodh-api-4.0.1-0.20170210160347.e062a0a.el7ost.noarch How reproducible: 100% Steps to Reproduce: 1. Upgrade OSP10 overcloud to OSP11 overcloud Actual results: Overcloud upgrade fails: Error: /Stage[main]/Aodh::Db::Sync/Exec[aodh-db-sync]: Failed to call refresh: aodh-dbsync --config-file /etc/aodh/aodh.conf returned 1 instead of one of [0] Error: /Stage[main]/Aodh::Db::Sync/Exec[aodh-db-sync]: aodh-dbsync --config-file /etc/aodh/aodh.conf returned 1 instead of one of [0] Error: /Stage[main]/Gnocchi::Db::Sync/Exec[gnocchi-db-sync]: Failed to call refresh: gnocchi-upgrade --config-file /etc/gnocchi/gnocchi.conf --skip-storage returned 1 instead of one of [0] Error: /Stage[main]/Gnocchi::Db::Sync/Exec[gnocchi-db-sync]: gnocchi-upgrade --config-file /etc/gnocchi/gnocchi.conf --skip-storage returned 1 instead of one of [0] Expected results: aodh-dbsync --config-file /etc/aodh/aodh.conf gets run successfully Additional info: This is already fixed in upstream: https://review.openstack.org/#/c/431055/
> Additional info: > This is already fixed in upstream: > https://review.openstack.org/#/c/431055/ It's fixed in upstream *master*. It is not available in the stable/ocata branch. Please work with the Telemetry team to get it backported to stable ocata.
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-2017:1245