mistral db-sync error when upgrading undercloud from newton to ocata

[Yolanda Robla]

When performing a major upgrade in the undercloud, from newton to ocata, it is failing with the following error:

2017-11-10 10:43:00,891 INFO: Notice: /Stage[main]/Mistral::Db::Sync/Exec[mistral-db-sync]/returns: INFO [alembic.runtime.migration] Context impl MySQLImpl.
2017-11-10 10:43:00,892 INFO: Notice: /Stage[main]/Mistral::Db::Sync/Exec[mistral-db-sync]/returns: INFO [alembic.runtime.migration] Will assume non-transactional DDL.
2017-11-10 10:43:00,892 INFO: Notice: /Stage[main]/Mistral::Db::Sync/Exec[mistral-db-sync]/returns: ERROR [alembic.util.messaging] Can't locate revision identified by '021'
2017-11-10 10:43:00,893 INFO: Notice: /Stage[main]/Mistral::Db::Sync/Exec[mistral-db-sync]/returns: FAILED: Can't locate revision identified by '021'
2017-11-10 10:43:00,893 INFO: Error: mistral-db-manage --config-file=/etc/mistral/mistral.conf upgrade head returned 255 instead of one of [0]
2017-11-10 10:43:00,894 INFO: Error: /Stage[main]/Mistral::Db::Sync/Exec[mistral-db-sync]/returns: change from notrun to 0 failed: mistral-db-manage --config-file=/etc/mistral/mistral.conf upgrade head returned 255 instead of one of [0]
2017-11-10 10:44:48,254 INFO: Notice: /Stage[main]/Mistral::Db::Sync/Exec[mistral-db-sync]/returns: INFO [alembic.runtime.migration] Context impl MySQLImpl.
2017-11-10 10:44:48,255 INFO: Notice: /Stage[main]/Mistral::Db::Sync/Exec[mistral-db-sync]/returns: INFO [alembic.runtime.migration] Will assume non-transactional DDL.
2017-11-10 10:44:48,255 INFO: Notice: /Stage[main]/Mistral::Db::Sync/Exec[mistral-db-sync]/returns: ERROR [alembic.util.messaging] Can't locate revision identified by '021'
2017-11-10 10:44:48,256 INFO: Notice: /Stage[main]/Mistral::Db::Sync/Exec[mistral-db-sync]/returns: FAILED: Can't locate revision identified by '021'
2017-11-10 10:44:48,256 INFO: Error: /Stage[main]/Mistral::Db::Sync/Exec[mistral-db-sync]: Failed to call refresh: mistral-db-manage --config-file=/etc/mistral/mistral.conf upgrade head returned 255 instead of one of [0]
2017-11-10 10:44:48,257 INFO: Error: /Stage[main]/Mistral::Db::Sync/Exec[mistral-db-sync]: mistral-db-manage --config-file=/etc/mistral/mistral.conf upgrade head returned 255 instead of one of [0]

Then finally:

2017-11-10 10:59:08,892 INFO: + echo 'puppet apply exited with exit code 6'
2017-11-10 10:59:08,892 INFO: puppet apply exited with exit code 6
2017-11-10 10:59:08,892 INFO: + '[' 6 '!=' 2 -a 6 '!=' 0 ']'
2017-11-10 10:59:08,893 INFO: + exit 6
2017-11-10 10:59:08,893 INFO: [2017-11-10 10:59:08,891] (os-refresh-config) [ERROR] during configure phase. [Command '['dib-run-parts', '/usr/libexec/os-refresh-config/configure.d']' returned non-zero exit status 1]
2017-11-10 10:59:08,893 INFO:
2017-11-10 10:59:08,893 INFO: [2017-11-10 10:59:08,892] (os-refresh-config) [ERROR] Aborting...
2017-11-10 10:59:08,901 ERROR:

[Yolanda Robla (yolanda.robla)]

mistral --version
mistral 3.0.2

[Yolanda Robla (yolanda.robla)]

rpm -qa | grep mistral
openstack-mistral-engine-4.0.2-1.el7.noarch
puppet-mistral-10.3.1-1.el7.noarch
openstack-mistral-api-4.0.2-1.el7.noarch
python2-mistralclient-3.0.2-1.el7.noarch
openstack-mistral-executor-4.0.2-1.el7.noarch
openstack-mistral-common-4.0.2-1.el7.noarch
python-mistral-tests-4.0.2-1.el7.noarch
python-openstack-mistral-4.0.2-1.el7.noarch

[mathieu bultel (mat-bultel)]

So looks like the delorean repo is still under newton, that probably explain why the db migration failed:
http://pastebin.test.redhat.com/531160

[Yolanda Robla (yolanda.robla)]

I followed upgrade instructions, installing the centos-release-openstack-ocata, then i launched undercloud upgrade. But seems it was conflicting somehow with the existing delorean newton repo, and packages not correctly updated

[Adriano Petrich (apetrich)]

I'm unable to reproduce. I followed https://docs.openstack.org/tripleo-docs/latest/install/installation/updating.html and did a minor upgrade first that didn't change anything just to be sure and a major upgrade newton to ocata. rdo-cloud had some connectivity issues and I had to do it 3 times (could not connect the mirrors, no connectivity, and it worked) for it to finish but it worked and didn't get the mistral error.

[Adriano Petrich (apetrich)]

Moving to invalid. If this happens again please reopen the ticket