Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1597279

Summary:	Unable to start gnocchi-api after OSP11 -> OSP12 upgrade
Product:	Red Hat OpenStack	Reporter:	Alex Stupnikov <astupnik>
Component:	openstack-gnocchi	Assignee:	Mehdi ABAAKOUK <mabaakou>
Status:	CLOSED ERRATA	QA Contact:	Sasha Smolyak <ssmolyak>
Severity:	high	Docs Contact:
Priority:	urgent
Version:	12.0 (Pike)	CC:	apevec, dprince, dwojewod, ipetrova, jamsmith, jsaucier, jschluet, lhh, mabaakou, mlehmann, pcaruana, pkilambi, pmorey, pneedle, ssmolyak
Target Milestone:	z3	Keywords:	Triaged, ZStream
Target Release:	12.0 (Pike)
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:	openstack-gnocchi-4.0.6-1.el7ost	Doc Type:	Bug Fix
Doc Text:	This update fixes an issue that previously caused Gnocchi database schema update failures during upgrade from OSP11 to OSP12.	Story Points:	---
Clone Of:
Clones:	1614343 (view as bug list)		Environment:
Last Closed:	2018-08-20 12: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:	1614343

Description Alex Stupnikov 2018-07-02 12:35:16 UTC

Description of problem:

Customer is unable to connect to gnocchi-api with standard openstckclient: he gets 500 Internal Server Error instead of valid reply. It looks like this issue is caused by lack of configured number of sack, since I can see spam of the following messages in /var/log/containers/gnocchi/app.log file:

ERROR    gnocchi.storage.incoming._carbonara: Unable to detect the number of storage sacks. Ensure gnocchi-upgrade has been executed: int() argument must be a string or a number, not 'NoneType'


I can see that "gnocchi_db_sync" container was executed with appropriate gnocchi-upgrade command, but this didn't helped.


When I have asked customer to manually execute gnocchi-upgrade command and provide its output, customer reported that command failed on "Upgrading indexer" step with "DBNonExistentConstraint" exception. Please take a look at attached gnocchi-upgrade_cli.log for detailed output.


There is no fresh information in "/var/log/gnocchi/gnocchi-upgrade.log" file, but I also can see that previous DB migration (looks like OSP10 -> OSP 11) failed with an error that is exactly the same as the one reported in bug #1425464. Please take a look at attached gnocchi-upgrade.log.

It looks like this issue was ignored and gnocchi worked well until customer  updated env to RHOSP12.


As a result, I would like to ask you to provide recommended steps to fix this issue. What should we do to finish DB migration?

Comment 5 Mehdi ABAAKOUK 2018-07-05 19:29:24 UTC

This is a known issue. Next Gnocchi 4.0 release will fix it. I will push for having it quickly.

Comment 12 Sasha Smolyak 2018-08-01 11:40:49 UTC

The 4.0.6 release is in puddle, gnocchi-api is up. Fixed

Comment 20 Dariusz Wojewódzki 2018-08-09 12:24:48 UTC

Please also provide the instruction on how to apply this fix on Customer containers.

Comment 44 errata-xmlrpc 2018-08-20 12:54:47 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/RHBA-2018:2522