[update] Openstack cluster update failed: /usr/bin/murano-db-manage --config-file=/etc/murano/murano.conf upgrade returned 1 instead of one of [0]

Bug #1367785 reported by Artem Panchenko
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Won't Fix
High
Dmitry Ilyin

Bug Description

This issue was caught after upgrade from 5.0 to 5.1 using custom upgrade tarball with the following patches:

https://review.openstack.org/#/c/120127/
https://review.openstack.org/#/c/119105/

Fuel version info:

http://paste.openstack.org/show/109537/

Steps to reproduce:

1. Create new cluster (CentOS, HA, NeutronGRE, Ceph for Volumes, Sahara, Murano)
2. Add 3 controller+ceph and 2 compute+cinder nodes. Deploy changes
3. Upgarde master node to 5.1. Run environment update to 5.0.2

Expected result:

- cluster successfully updated

Actual:

- update failed

Update failed on first controller (node-1), here is the part of its puppet logs:

http://paste.openstack.org/show/109538/

And output of failed command (executed manually):

http://paste.openstack.org/show/109536/

Revision history for this message
Artem Panchenko (apanchenko-8) wrote :
Changed in fuel:
assignee: nobody → MOS Murano (mos-murano)
ruhe (ruhe)
Changed in fuel:
assignee: MOS Murano (mos-murano) → Dmitry Teselkin (teselkin-d)
Changed in fuel:
status: New → Confirmed
Revision history for this message
Dmitry Teselkin (teselkin-d) wrote :

Different commands used for db-sync during installation / upgare, see http://paste.openstack.org/show/110059/

Mike Scherbakov (mihgen)
tags: added: experimental
Changed in fuel:
status: Confirmed → In Progress
Revision history for this message
Dmitry Teselkin (teselkin-d) wrote :

Murano in FUEL 5.0.1 and 5.0.2 uses different database upgrade tools (sqlalchemy in 5.0.1 and alembic in 5.0.2).
Because of this there is no way to perform upgrade from 5.0.1 to 5.0.2 or downgrade from 5.0.2 to 5.0.1.
The command that performs database migration will fail in both cases.

The only workaround is to drop entire Murano database before upgrade / downgrade and re-create it again.

The user must be warned that they will lost all their Murano-related data and settings.

Steps to perform 5.0.1 -> 5.0.2 upgrade:

1. Stop active murano-api services
2. Drop database murano
3. Create empty database murano
4. Run database migrations
5. Start murano-api services

Steps to perform 5.0.2 -> 5.0.1 downgrade:

1. Stop active murano-api services
2. Drop database murano
3. Create empty database murano
4. Run database migrations
5. Start murano-api services

Revision history for this message
Serg Melikyan (smelikyan) wrote :

This issue should be assigned to Dmitry Ilyin

Changed in fuel:
assignee: Dmitry Teselkin (teselkin-d) → nobody
Changed in fuel:
assignee: nobody → Dmitry Ilyin (idv1985)
Changed in fuel:
milestone: 5.1 → 5.0.3
Revision history for this message
Dmitry Ilyin (idv1985) wrote :

I've made hook that recreates the murano database on update and will add it to the pre-update Astute hooks.

Revision history for this message
Serg Melikyan (smelikyan) wrote :

Dmitry Ilyin, can you provide change-request for that?

Revision history for this message
Dmitry Ilyin (idv1985) wrote :

I have included this to deployment tasks https://review.openstack.org/#/c/127284/5/deployment/tasks/astute/lib/migration.rb,cm
But looks like the new tasks system is not getting into 6.0 so we'll have to backport it to the Astute hooks.

Revision history for this message
Matthew Mosesohn (raytrac3r) wrote :

Dmitry do you have a status update? Can we get this before release?

Revision history for this message
Dmitry Ilyin (idv1985) wrote :

I'll try to backport this fix https://review.openstack.org/#/c/127284/5/deployment/tasks/astute/lib/migration.r to Astute's pre-update hook.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix proposed to fuel-library (master)

Related fix proposed to branch: master
Review: https://review.openstack.org/134926

Dmitry Ilyin (idv1985)
summary: - [upgrade] Openstack cluster update failed: /usr/bin/murano-db-manage
+ [update] Openstack cluster update failed: /usr/bin/murano-db-manage
--config-file=/etc/murano/murano.conf upgrade returned 1 instead of one
of [0]
Revision history for this message
Stanislaw Bogatkin (sbogatkin) wrote :

We do not support such type of patching anymore. Closed.

Changed in fuel:
status: In Progress → Won't Fix
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on fuel-library (master)

Change abandoned by Igor Shishkin (<email address hidden>) on branch: master
Review: https://review.openstack.org/134926
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.