© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
73416ba
(Get the code!)
Problem seems to be around updating the existing plan during the deployment from the CLI. This error has only occurred in multinode jobs (not ovb). The first occurrences started on this patch:
https:/
The error does not happen 100% of the time, but it can be seen on some earlier CI results of that patch.
We've tried several workarounds to to address the problem:
reducing the mistral workers (since ovb has less vcpu's than multinode and does not see this issue):
https:/
that failed the same way.
Also tried deleting the existing plan before starting the deployment:
https:/
That also failed with the messaging timeout, but exposed the issue that the default plan may not yet finish being created before we start the overcloud deployment. When we start the deployment and try to then update the plan, we could be tripping over ourselves and causing this error.
Dougal has a patch to wait to make sure the default plan is created which may be the true fix:
https:/
But that was not being tested appropriately due to:
https:/
where we were not testing patches with delorean due to unintentionally deleting the delorean db.
As of now, we are attempting to land this revert:
https:/
However, given the other CI issue with not testing patches correctly we can't land that revert until we temporarily make the multinode job nonvoting:
https:/
Once that project-config patch lands, we plan to land these 3 patches:
https:/
https:/
https:/
we will then re-enable the multinode job as voting.