Merge ~tribaal/cloud-init:fix/exoscale-datasource-wait-timeout into cloud-init:master
Proposed by
Chris Glass
Status: | Merged |
---|---|
Approved by: | Scott Moser |
Approved revision: | 46310972f0ce5513b93d1c3c813cf6ef0b62f2f4 |
Merge reported by: | Server Team CI bot |
Merged at revision: | not available |
Proposed branch: | ~tribaal/cloud-init:fix/exoscale-datasource-wait-timeout |
Merge into: | cloud-init:master |
Diff against target: |
13 lines (+2/-0) 1 file modified
cloudinit/sources/DataSourceExoscale.py (+2/-0) |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Server Team CI bot | continuous-integration | Approve | |
Dan Watkins | Approve | ||
Review via email: mp+374643@code.launchpad.net |
Description of the change
exoscale: Increase url_max_wait to 120s.
The exoscale datasource defines a shorter timeout than the default (10)
but did not override url_max_wait, resulting in a single attempt being
made to wait for the metadata service.
In some rare cases, a race condition means the route to the metadata
service is not set within 10 seconds, and more attempts should be made.
This sets the url_max_wait for the datasource to 120.
To post a comment you must log in.
Note: retrying 12 times on average might be overkill here - but we rather be pessimistic and add a lot of buffer.