Bug 1416502

Summary: Undercloud upgrade fails during aodh-db-sync: ProgrammingError: (pymysql.err.ProgrammingError) (1146, u"Table 'ceilometer.alarm_change' doesn't exist") [SQL: u'ALTER TABLE alarm_change ADD COLUMN timestamp_ts DATETIME(6)']
Product: Red Hat OpenStack Reporter: Marius Cornea <mcornea>
Component: instack-undercloudAssignee: Pradeep Kilambi <pkilambi>
Status: CLOSED ERRATA QA Contact: Omri Hochman <ohochman>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 11.0 (Ocata)CC: dbecker, jdanjou, jschluet, mandreou, mburns, morazi, pkilambi, rhel-osp-director-maint, sclewis
Target Milestone: rcKeywords: Triaged
Target Release: 11.0 (Ocata)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: instack-undercloud-6.0.0-0.20170120171137.c891931.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-05-17 19:43:26 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 Marius Cornea 2017-01-25 16:12:36 UTC 
Description of problem:
Undercloud upgrade fails during aodh-db-sync: ProgrammingError: (pymysql.err.ProgrammingError) (1146, u"Table 'ceilometer.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):
instack-undercloud-6.0.0-0.20170120171137.c891931.el7ost.noarch

How reproducible:
100%

Steps to Reproduce:
1. Upgrade undercloud

Actual results:
Fails during aodh-db-sync:

2017-01-25 11:00:17,233 INFO: Error: /Stage[main]/Aodh::Db::Sync/Exec[aodh-db-sync]/returns: change from notrun to 0 failed: aodh-dbsync --config-file /etc/aodh/aodh.conf returned 1 instead of one of [0]
 

Expected results:
Upgrade completes ok.

Additional info:
Comment 1 Julien Danjou 2017-01-26 13:45:33 UTC 
The question is: why is Ceilometer database referenced here?
Comment 8 errata-xmlrpc 2017-05-17 19:43:26 UTC 
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