Comment 12 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 | #12 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
It's not about input to the *workflow*, it's about input to the *action*. I think what we have is a desync within mistral containers. Likely we have this patch in one of the mistral containers (e.g. API or engine) but we don't have it in another (e.g. executor):
https:/
What i said earlier on this bug still holds true i think -- all we need is fresh content of containers, AFAICT. When i deployed with `update_containers: true`, the problem disappeared in my dev env.
If we promoted recently and it didn't fix the problem, we should to check our promotion process (did we leave out some image by accident maybe?).