Description of problem:
We are moving graphite-web from 0.9.X to 1.1.4-1. So as per the new version of graphite-web sync DB initialization should be changed in tendrl-ansible.
Version-Release number of selected component (if applicable):
Initialization command for graphite-web-1.1.4-1 is changed to we need to replace old graphite db initialization command with new one in tendrl-ansible.
Steps to Reproduce:
New version of graphite won't work with current initialization command
Tendrl ansible able to initialize graphite db with a new version of graphite-web.
PR under reivew: https://github.com/Tendrl/tendrl-ansible/pull/134
If old graphite is updated to the new version:
then we need to do some extra step:
1. PYTHONPATH=$GRAPHITE_ROOT/webapp/ django-admin migrate --fake-initial --settings=graphite.settings --run-syncdb
if any app faile with table already exit
(E.g) dashboard app is failing then run fake command for that
PYTHONPATH=$GRAPHITE_ROOT/webapp/ django-admin migrate --fake dashboard --settings=graphite.settings
2. then again continue step 1
Providing QA ack, this is about making sure that installation works with new graphite stack (BZ 1658702).
Note that qe team needs to make sure that this change doesn't break update path (separate BZ will be
created with exact description of a case if problem with this is noticed during testing.
Initialization command in tendrl-ansible is changed to `django-admin migrate --settings=graphite.settings --run-syncdb` and installation works fine. --> VERIFIED
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.