Comment 5 for bug 1349377

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.