Bug 1386613 - [Docs][Manual Installation] Replace gnocchi-dbsync command with gnocchi-upgrade
Summary: [Docs][Manual Installation] Replace gnocchi-dbsync command with gnocchi-upgrade
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: documentation
Version: 9.0 (Mitaka)
Hardware: Unspecified
OS: Linux
unspecified
high
Target Milestone: async
: 10.0 (Newton)
Assignee: Lukas Ruzicka
QA Contact: Petr Kovar
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-19 09:55 UTC by Francisco Javier Lopez Y Grueber
Modified: 2017-01-06 15:02 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-01-06 15:02:53 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Francisco Javier Lopez Y Grueber 2016-10-19 09:55:11 UTC 
Description of problem:

Gnocchi Documentation Bug: 

openstack-gnocchi-indexer-sqlalchemy-2.1.3-3.el7ost.noarch does not contains gnocchi-dbsync.

Our Installation Reference for Mitaka metions gnocchi-dbsync to initialize the gnocchi backend. 

14.2. Initialize Time-Series-Database-as-a-Service
Initialize the indexer:
# gnocchi-dbsync


Version-Release number of selected component (if applicable):


How reproducible:

Always

Steps to Reproduce:
1. 

rpm -ql openstack-gnocchi-indexer-sqlalchemy
/usr/bin/gnocchi-upgrade
 
2.
3.

Actual results:

Executing gnocchi-upgrade installs "some" of the expected tables, except the ones needed by metricd and statsd. 

Expected results:

All needed tables are created as expected. 

Additional info:
Comment 2 Lucy Bopf 2016-12-21 08:11:20 UTC 
Assigning to Lukas for review.
Comment 3 Lukas Ruzicka 2016-12-22 08:42:54 UTC 
The mentioned command only occurred in the Docs once. I changed it into "gnocchi-upgrade" in both 9 and 10 versions.
Comment 4 Lukas Ruzicka 2017-01-06 15:02:53 UTC 
Updated guides have been published.
Note You need to log in before you can comment on or make changes to this bug.