Comment 15 for bug 1786764

Revision history for this message
Jiří Stránský (jistr) wrote : Re: tripleo-ci-centos-7-scenario000-multinode-oooq-container-updates times out on prepare

The mistral action definitions are in its database. Is it possible that we populate the database with non-updated mistral code (pre- August 13) and then we actually run Mistral processes with an updated container (post- August 15), without re-running `sudo mistral-db-manage populate`? That would result in such error messages i think.