Comment 2 for bug 1781286
Revision history for this message
| Matt Riedemann (mriedem) wrote Re: CantStartEngineError in cell conductor during rebuild | #2 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
I don't see how this could happen. When we initially schedule a server, we populate the retry field in the filter_properties and set num_attempts to 1:
https:/
We do the same here with what should be the same filter_properties dict passed from conductor -> compute -> conductor during the reschedule loop:
https:/
That second call to populate_retry should increment num_attempts to 2:
https:/
The only thing I can figure is maybe you have the max_attempts config option value set to 1 or you're forcing the host/node during the server create?
https:/
In that case we don't set the retry entry in filter_properties.