summaryrefslogtreecommitdiff
path: root/templates/sources.list.debian.tmpl
diff options
context:
space:
mode:
authorJohnson Shi <Johnson.Shi@microsoft.com>2020-10-16 08:54:38 -0700
committerGitHub <noreply@github.com>2020-10-16 11:54:38 -0400
commit8766784f4b1d1f9f6a9094e1268e4accb811ea7f (patch)
treed654af968ed5b185402802a3cafea7c7357e0b26 /templates/sources.list.debian.tmpl
parentc0e8480678e3a9173c9de1271f651fb3ba375f22 (diff)
downloadvyos-cloud-init-8766784f4b1d1f9f6a9094e1268e4accb811ea7f.tar.gz
vyos-cloud-init-8766784f4b1d1f9f6a9094e1268e4accb811ea7f.zip
DataSourceAzure: write marker file after report ready in preprovisioning (#590)
DataSourceAzure previously writes the preprovisioning reported ready marker file before it goes through the report ready workflow. On certain VM instances, the marker file is successfully written but then reporting ready fails. Upon rare VM reboots by the platform, cloud-init sees that the report ready marker file already exists. The existence of this marker file tells cloud-init not to report ready again (because it mistakenly assumes that it already reported ready in preprovisioning). In this scenario, cloud-init instead erroneously takes the reprovisioning workflow instead of reporting ready again.
Diffstat (limited to 'templates/sources.list.debian.tmpl')
0 files changed, 0 insertions, 0 deletions