Fuel doesn't run murano db migrations

[Timur Sufiev]

1) Connect to fuel node-1.

2) Run the following commands:
mysql
mysql> connect murano;
mysql> show tables;
Notice that there are no tables at all.

3) Then exit mysql, run
python /usr/lib/python2.7/dist-packages/muranoapi/cmd/manage.py --config-file /etc/murano/murano.conf db-sync

repeat step 2) and notice that murano tables appeared in db.

[Timur Sufiev (tsufiev-x)]

Fuel image info:

{"build_id": "2014-07-28_12-27-17", "ostf_sha": "8c328521b1444f22c50463b9432193e20ed33813", "build_number": "494", "auth_required": true, "api": "1.0", "nailgun_sha": "83cc9ed44ebc8dd97248483b6d414ebbc4cff3c0", "production": "docker", "fuelmain_sha": "9adfbf5a52cedbdd16ec1a74f6c44c5b3419b87c", "astute_sha": "aa5aed61035a8dc4035ab1619a8bb540a7430a95", "feature_groups": ["mirantis"], "release": "5.1", "fuellib_sha": "d1c7f67b3cf51978d3178c8666ea398f2477dcb5"}

[Timur Nurlygayanov (tnurlygayanov)]

https://github.com/stackforge/fuel-library/blob/master/deployment/puppet/murano/manifests/api.pp#L140

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/110003

[Meg McRoberts (dreidellhasa)]

Please clarify what needs to go in the 5.0.1 Release Notes. The work around is:
after Fuel upgrade completes, if Murano is running in the environment, they need to stop My SQL
and run the commands in #3 above on the primary Controller node, then restart MySQL..

Is that it or do they need to run this command on every Controller node or elsewhere?

[Timur Sufiev (tsufiev-x)]

Meg, did you mean 5.1 Release Notes? The bug was filed for this milestone, so I thought 5.0.1 is a typo.

Anyways, I don't think we should fix that bug as is or add some release notes for it, because:
1) the bug is caused by the puppet scripts relying on alembic migrations already being merged into Murano code in 5.1 branch, which is not the case
2) we need that alembic code in Murano in 5.1 more desperately than any other Murano patch being backported into 5.1, there is already change request for it in 5.1: https://gerrit.mirantis.com/#/c/18948/
3) the problem is that currently Murano's alembic patch fails because of some not resolved package dependency, we still do not fully understand the issue (see https://docs.google.com/a/mirantis.com/spreadsheets/d/1qvqyIan8hSbi3-4ZWlYijLcfXar0BGzqZGqawPHH8Bo/edit?pli=1#gid=1258923653, patch "Added DB migrations on Alembic")
4) I propose to do not anything with that bug until we sort out the previous issue, and once the Murano's alembic patch is merged, close this one as invalid.

Sorry for not writing this earlier, so all involved parties could spare their efforts, but IMO that's the best course of actions.

[Mike Scherbakov (mihgen)]

Lowering priority to High, as:
1) bug affects only of the OpenStack features (all OpenStack components are deployed fine, and only one component doesn't work, which is Murano)
2) there is existing workaround

Folks, let's understand how do we miss this issue in our tests, including OSTF & system tests.

[OpenStack Infra (hudson-openstack)]

Change abandoned by Bogdan Dobrelya (<email address hidden>) on branch: master
Review: https://review.openstack.org/110003

[Timur Sufiev (tsufiev-x)]

This one will be fixed as soon as bug #1348594 is fixed.