diff options
| author | Jason Zions <jasonzio@microsoft.com> | 2019-01-15 17:05:47 +0000 |
|---|---|---|
| committer | Server Team CI Bot <josh.powers+server-team-bot@canonical.com> | 2019-01-15 17:05:47 +0000 |
| commit | f19dc8fa62d4fd8de33311c3c75c5b6da440bebe (patch) | |
| tree | 103d0d79391a947975f0971040cb674b6473dd4a | |
| parent | 5f49ee0f3bdc9b3ebcc71b344b3918d4ef58c989 (diff) | |
| download | vyos-cloud-init-f19dc8fa62d4fd8de33311c3c75c5b6da440bebe.tar.gz vyos-cloud-init-f19dc8fa62d4fd8de33311c3c75c5b6da440bebe.zip | |
[Azure] Increase retries when talking to Wireserver during metadata walk
Testing startup of large numbers of VMs (of varying distros) in Azure
shows that 3 retries results in a small percentage of failed VMs.
Increasing that by a few dramatically decreases the occurrence of
provisioning timeout errors. The initial choice of "3 retries" was
uninformed by heavy testing. Also, the alternate provisioning
mechanism for Azure (waagent) retries the Wireserver crawl without
limit. 10 retries seems a more reasonable choice.
| -rw-r--r-- | cloudinit/sources/DataSourceAzure.py | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/cloudinit/sources/DataSourceAzure.py b/cloudinit/sources/DataSourceAzure.py index 46efca4a..a4f998b3 100644 --- a/cloudinit/sources/DataSourceAzure.py +++ b/cloudinit/sources/DataSourceAzure.py @@ -416,7 +416,7 @@ class DataSourceAzure(sources.DataSource): raise sources.InvalidMetaDataException(msg) ret = self._reprovision() imds_md = get_metadata_from_imds( - self.fallback_interface, retries=3) + self.fallback_interface, retries=10) (md, userdata_raw, cfg, files) = ret self.seed = cdev crawled_data.update({ |