diff options
author | Johnson Shi <Johnson.Shi@microsoft.com> | 2020-11-18 09:34:04 -0800 |
---|---|---|
committer | GitHub <noreply@github.com> | 2020-11-18 12:34:04 -0500 |
commit | d807df288f8cef29ca74f0b00c326b084e825782 (patch) | |
tree | 4102e9fda39c03da57cd875692015c41b73f5055 /cloudinit/reporting | |
parent | 96d21dfbee308cd8fe00809184f78da9231ece4a (diff) | |
download | vyos-cloud-init-d807df288f8cef29ca74f0b00c326b084e825782.tar.gz vyos-cloud-init-d807df288f8cef29ca74f0b00c326b084e825782.zip |
DataSourceAzure: send failure signal on Azure datasource failure (#594)
On systems where the Azure datasource
is a viable platform for crawling metadata,
cloud-init occasionally encounters fatal
irrecoverable errors during the crawling
of the Azure datasource.
When this happens, cloud-init crashes,
and Azure VM provisioning would fail.
However, instead of failing immediately,
the user will continue seeing provisioning
for a long time until it times out with
"OS Provisioning Timed Out" message.
In these situations, cloud-init should
report failure to the Azure datasource
endpoint indicating provisioning failure.
The user will immediately see provisioning
terminate, giving them a much better
failure experience instead of pointlessly
waiting for OS provisioning timeout.
Diffstat (limited to 'cloudinit/reporting')
0 files changed, 0 insertions, 0 deletions