Comment 4 for bug 1674770
Revision history for this message
| Ben Nemec (bnemec) wrote Re: Timeout passed to overcloud deploy not effective | #4 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
Oh, crud. I totally missed that the create completed and moved on to the update in this job. I think you're right that we need a shorter timeout for update.
Looking at the graphite metrics for the update job it looks like the average is around 40 minutes when the cloud is heavily loaded. We'd probably need to go at least 45 to account for normal runtime variations.